Hi Yogesh, On 04.10.19, 00:48, "yogesh upadhyay" <[email protected]> wrote: > - what's the role of lease check if you are using Mysql.
The lease check is part of the clusterId mechanism that gives each cluster node a unique id. This is not specific to the DocumentStore backend in use and is needed for any backend. See also https://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html#cluster-node-metadata > - Can we disable leasecheck for read repository ? This is already the case when you construct a read-only DocumentNodeStore [0]. > - What is the consequence of disabling lease check in prod ? (repository > corruption ?) One of the problems that can occur are described here: https://issues.apache.org/jira/browse/OAK-3883 Consistency can be at risk when lease checks are disabled and recovery is performed by another cluster node even though the (temporarily?) unresponsive cluster node is still alive and then continues to write. There are also implications on the Sling Topology when lease checks are disabled. The system may end up in a situation where multiple leaders exist. Regards Marcel [0] https://github.com/apache/jackrabbit-oak/blob/jackrabbit-oak-1.18.0/oak-store-document/src/main/java/org/apache/jackrabbit/oak/plugins/document/DocumentNodeStoreBuilder.java#L267
