High Availability DB question - 未名空间MITBBS历史存档

国际科技财经博客移民网络热点娱乐民生时事公众号

Redian新闻

>未名空间

>Java - 爪哇娇娃

High Availability DB question

High Availability DB question# Java - 爪哇娇娃

J*o2014-06-08 07:06

1 楼

大家好，我想向大家请教一些关于申请移民的问题。
我去年10月份拿到了H1B签证，我从F2转过来的，我老公现在还是F1，现在在准备找工
作，基本上会在5月份毕业。我现在所在的公司比较小，办理移民是可以的，但是可能
时间会很长（sorry，我也不知道公司大小和办理移民时间长短有没有关联，只是这么
猜测的），我老公如果能找到工作的话应该会是在学校这样的地方，感觉办理移民是不
是应该好办一些。
不知道像这样的情况，可不可以我先在我公司这里申请上，然后等我老公这里稳定下来
了，再转成我老公主办理？
另外，不知道大家能不能推荐一个这方面的律师。
谢谢大家的帮忙。

l*i2014-06-08 07:06

2 楼

每次听完这首曲子就觉得的自己还有好长的路要走。

F*n2014-06-08 07:06

3 楼

If my master server failed how to handle data that have NOT been replicated
to the slave servers?

s*u2014-06-08 07:06

4 楼

可以我先在我公司这里申请上，然后等我老公这里稳定下来
了，再转成我老公主办理
EB1 takes 1 years, EB2 and EB3 takes 8-10 years.

s*l2014-06-08 07:06

5 楼

cool~

【在 l******i 的大作中提到】

: 每次听完这首曲子就觉得的自己还有好长的路要走。

g*g2014-06-08 07:06

6 楼

Depends on how the master server fails, if the data is available in commit
log, restarting the server can fix it.
If it's harddisk failure, however, obviously data is lost.

replicated

【在 F****n 的大作中提到】

: If my master server failed how to handle data that have NOT been replicated
: to the slave servers?

l*i2014-06-08 07:06

7 楼

是啊，被他的感情和手指震撼。

【在 s******l 的大作中提到】

: cool~

F*n2014-06-08 07:06

8 楼

有啥应对办法

【在 g*****g 的大作中提到】

: Depends on how the master server fails, if the data is available in commit
: log, restarting the server can fix it.
: If it's harddisk failure, however, obviously data is lost.
:
: replicated

O*a2014-06-08 07:06

9 楼

每次听他这个版本就郁闷这么凝重大气的原声被改编成了这样，知名度反高过原声

w*z2014-06-08 07:06

10 楼

你是怎么ack写的, master node, 写了，就ack?

【在 F****n 的大作中提到】

: 有啥应对办法

m*l2014-06-08 07:06

11 楼

COOL~~

g*e2014-06-08 07:06

12 楼

http://en.wikipedia.org/wiki/Paxos_(computer_science)

commit

【在 F****n 的大作中提到】

: 有啥应对办法

F*n2014-06-08 07:06

13 楼

Right, asynchronous replication.
I know it is not possible to have strict atomic consistency.
It is called "eventual consistency", right:)
But I would like to know what is the best practice to deal with (not solve)
this kind of situations.

【在 w**z 的大作中提到】

: 你是怎么ack写的, master node, 写了，就ack?

F*n2014-06-08 07:06

14 楼

Good read, thanks!

【在 g**e 的大作中提到】

: http://en.wikipedia.org/wiki/Paxos_(computer_science)
:
: commit

g*g2014-06-08 07:06

15 楼

In principle, you need multiple nodes to ack on a transaction if the data is
super critical. Obviously there's a performance penalty here.

【在 F****n 的大作中提到】

: Right, asynchronous replication.
: I know it is not possible to have strict atomic consistency.
: It is called "eventual consistency", right:)
: But I would like to know what is the best practice to deal with (not solve)
: this kind of situations.

w*z2014-06-08 07:06

16 楼

as goodbug said, and C* way of handling, it is written in commit log every
10 secs and replicated to other nodes. if the hard drive doesn't fail, you
could lose up to 10 secs of writes. if your HD is gone, you will lose all
unreplicated data.

【在 F****n 的大作中提到】

g*g2014-06-08 07:06

17 楼

The fsync interval can be configured though.

every

【在 w**z 的大作中提到】

: as goodbug said, and C* way of handling, it is written in commit log every
: 10 secs and replicated to other nodes. if the hard drive doesn't fail, you
: could lose up to 10 secs of writes. if your HD is gone, you will lose all
: unreplicated data.