Thanks Julian, could you help me to find that system property?
In my application, when I create DocumentNodeStore I'am able to set the leasecheckmode properly, but using oak-upgrade I have no control about that instanciation, so a system property is necessary I think. Thank you Cordiali saluti / Best regards, Raffaele Gambelli Application Architect ________________________________ From: Julian Reschke <[email protected]> Sent: Monday, October 27, 2025 11:05 AM To: [email protected] <[email protected]> Subject: Re: About leaseCheckMode Am 27.10.2025 um 10:22 schrieb Raffaele Gambelli: > Hi all, > > I don't understand why the lease check mode mechanism is used even in an > environment with only one oak node, Shouldn't this mechanism only be > useful when there are at least two oak nodes, i.e. when there is a cluster? AFAIK this is because Oak does not know how many nodes are/will be active. > Let me give you an example. I am trying oak-upgrade to migrate a > jackrabbit 2.x repository to an oak repository with mongodb. > During the migration, if I leave the computer inactive because, for > example, I go to lunch, when I return I find that the procedure has > failed because the only node was considered dead because the lease was > not renewed. What is the point of that? > Thanks I *believe* there's a system property to disable the check exactly for that use case. Best regards, Julian
