Hi Bruce, Anthony, Thank you very much for your replies. One more question - could this time difference create some inconsistence in case of replicated regions? Will this affect conflict checking that happens before region updates to detect and resolve concurrent and out-of-order updates?
Thanks, Vahram. From: Bruce Schuchardt <bschucha...@pivotal.io> Sent: Wednesday, July 11, 2018 7:52 PM To: user@geode.apache.org Subject: Re: Time difference between cluster members The only time-sync thing I can think of is tombstone expiration. The concurrency control mechanism creates tombstones when entries in the cache are destroyed. While there is a distributed garbage collection mechanism to take care of removing tombstones there is also a local check to see if a tombstone has expired, so you don't want to have big clock skews between your servers. On 7/11/18 2:34 AM, Vahram Aharonyan wrote: Hi All, Any input on this would be highly appreciated. Thanks, Vahram. From: Vahram Aharonyan <vaharon...@vmware.com><mailto:vaharon...@vmware.com> Sent: Friday, July 6, 2018 4:31 PM To: user@geode.apache.org<mailto:user@geode.apache.org> Subject: Time difference between cluster members Hi All, Could someone help to understand whether there is some threshold on time difference between Geode cluster members if they have the same time zone? Or all members should be in sync from time point of view for normal functioning? Thanks, Vahram.
