Hi, On 16/02/16 12:35, "[email protected] on behalf of Ian Boston" wrote: >Presumably, having a cluster node running behind real time will result in >lower throughput, making it critical to run NTP on all cluster nodes to >eliminate as much clock drift as possible ?
Yes, this is correct. Though, the clocks do not have to be in perfect sync. Each DocumentNodeStore runs background operations once a second. So, you probably won't notice any delays even when the clock difference is one second. >Also, does the current revision model behave with an eventually consistent >storage mechanism, or does Oak require that the underlying storage is >immediately consistent in nature ? In general a DocumentStore implementation must be strongly consistent, but there are API calls that allow to leverage an eventually consistent backend. E.g. there is a DocumentStore.find() variant with a maxCacheAge parameter. This allows the current MongoDocumentStore implementation to use a secondary for the read if applicable. IMO the API may likely have to be changed to better support such use cases. Related issues are OAK-2106 and OAK-3865. Regards Marcel
