Hi Abraham,
Thanks a lot for your reply. I really appreciate.
Regards,
Amr
--
View this message in context:
http://zookeeper-user.578899.n2.nabble.com/ZooKeeper-Time-Synchronization-tp7583217p7583236.html
Sent from the zookeeper-user mailing list archive at Nabble.com.
@Amr it looks like I did not see your last email.
1. I think that would certainly be ideal, but it is a really difficult
problem to solve.
2a. Nope
2b. Yup
On Mon, Jul 31, 2017, at 11:40, Abraham Fine wrote:
> @Amr -Sorry for the delayed response. I could be wrong but I don't
> think mtimes wou
@Amr -Sorry for the delayed response. I could be wrong but I don't
think mtimes would have any impact on anything.
What do you think could go wrong?
Abe
On Fri, Jul 21, 2017, at 11:56, Alexander Shraer wrote:
> As far as I understand:
>
> 1) no
> 2) yes
> 3) yes
> 4) yes
> 5) no, except for t
Any idea Guys on my last post, please?
Thanks!
--
View this message in context:
http://zookeeper-user.578899.n2.nabble.com/ZooKeeper-Time-Synchronization-tp7583217p7583232.html
Sent from the zookeeper-user mailing list archive at Nabble.com.
Thanks guys for your replies and prompt responses,
1) if mtime is just for user recording, then the user and all the elected
masters should be synchronized over the working period. Right?
2) Concenrning the MONOTONIC_CLOCK, excuse me, I have the following
confusion
a- Do we need to keep the MONOT
The general idea is to use time for availability but not correctness. So a
leader could be suspected as failed which may make the system unavailable
until a new one is elected but consistency is not affected.
Alex
On Fri, Jul 21, 2017 at 1:56 PM Michael Han wrote:
> One clarification on "System
One clarification on "System Time" here - ZK uses two type of time/clock
* The wall-clock time, which is recorded as part of zNode stats such as
mtime and is exposed to users.
* The monotonic clock which ZK uses in various uses (e.g. failure
detection) to measure intervals. Note in 3.4 ZK still us
mtime etc is exposed to user to provide basic stats info; ZK itself does
not use these times. These times will just be recorded as they are and
carried over and does not impact anything in case leader election etc
happens.
On Fri, Jul 21, 2017 at 11:30 AM, Amr wrote:
> Hi Abe,
>
> Thanks a lot f
Thanks for reply.
But as per I understand, in leader election, it has to wait for some amount
of time for leader proposal and voting using paxos. Which might happen when
one of the slave belive that current leader is dead (due to timeout for
leader response etc). The voting too will have some time
As far as I understand:
1) no
2) yes
3) yes
4) yes
5) no, except for the sync command (there is a jira open for that)
Others please correct me if I'm wrong
Thanks
Alex
On Fri, Jul 21, 2017 at 11:52 AM Sandeep Singh
wrote:
> Adding the Amr question.
> Few things which I want to add is:
>
> Do
Adding the Amr question.
Few things which I want to add is:
Does zookeeper uses System Time for below things
1) Leader election
2) Deciding a slave is available/alive or not.
3) Deciding leader/master is alive or not.
4) Deciding a transaction timeout etc.
5) Ordering the transaction etc.
regard
Hi Abe,
Thanks a lot for your reply and for the reference. Excuse me, I have a
comment and a request for clarification.
I see in the link you provided
"ZooKeeper doesn't use real time, or clock time, at all except to put
timestamps into the stat structure on znode creation and znode
modificati
Hi Amr-
ZooKeeper gets around time synchronization issues by using "ticks".
Please check out the time section in this doc for more information:
http://zookeeper.apache.org/doc/r3.4.0/zookeeperProgrammers.html
In short, except for adding metadata to znodes zookeeper does not use
real time at all.
13 matches
Mail list logo
