Consider that for some reason the session lease is expired and cannot be used. For example one scenario is that the the cluster node is removed from the clusterNodes collection (I couldn't find out all scenarios that this happens). What happens is that the background lease update thread finds this out and starts writing out exceptions. If we could somehow detect this status (e.g. with an observer), and reconnect the connection, I could recover the application from this state again. Is this possible? I'm using jackrabbit oak 1.6.1.
Regards On Mon, Aug 7, 2017 at 6:30 PM, Mostafa Mahdieh <m.mahd...@gmail.com> wrote: > Can anyone please help me on Marcel's comment? Is it already implemented? > I really need your help. > > On Sun, Aug 6, 2017 at 5:18 PM, Mostafa Mahdieh <m.mahd...@gmail.com> > wrote: > >> There is a comment here (https://issues.apache.org/jira/browse/OAK-3424) >> from Marcel Reutegger >> <https://issues.apache.org/jira/secure/ViewProfile.jspa?name=mreutegg>, >> suggesting that: >> >> *"I my view we should change the current behavior and prohibit a >> deployment where two cluster nodes are running with the same working >> directory and an > automatic clusterId is requested."* >> >> It seems that this behavior matches my scenario. How can I configure the >> oak connection such that this happens? >> >> On Sun, Aug 6, 2017 at 4:37 PM, Julian Reschke <julian.resc...@gmx.de> >> wrote: >> >>> On 2017-08-06 09:08, Mostafa Mahdieh wrote: >>> >>>> Thanks for your suggestions. >>>> >>>> I'm wondering what happens in the worst case if I disable the lease >>>> check. >>>> ... >>>> >>> >>> Repository corruption. >>> >>> What you need to find out is why the lease renewal fails, not how to >>> turn it off. :-) >>> >> >> >> >> -- >> Mostafa Mahdieh >> > > > > -- > Mostafa Mahdieh > -- Mostafa Mahdieh
