Hi Raffaele,
(this time to the list..)
Those logs indicate that the instance (which has clusterId 1 as the
thread name shows) was not updating its lease with the DocumentStore for
longer than what is configured as the lease timeout (default is 120
sec). This could be due to a range of things - what are frequent root
causes is the jvm process to be seemingly halted (eg by busy GC-ing when
nearly running out of memory), the thread or process blocked or delayed
due to some other reason or that the backend DocumentStore was not
writable due to performance issues, etc. Having an active lease is part
of the clustering mechanism - it allows all participants to see which
instances are active, which have crashed and require recovery etc. [0]
has some more docu on this.
If as you are saying you are running DocumentNodeStore in a static 1 VM
cluster and are certain there's never any other clusterId, then in fact
you could use LENIENT indeed. LENIENT is just not recommended in an
actual cluster. Where did you find the indication that you shouldn't use
LENIENT in this context?
Cheers,
Stefan
--
[0] -
https://jackrabbit.apache.org/oak/docs/nodestore/documentmk.html#cluster-node-metadata
On 14.10.24 10:50, Raffaele Gambelli wrote:
Hi all,
I would like to know more about leasing, please considering that I'm running
always with a single node, so I have no cluster or maybe it's considered a
cluster with one node.
I've found that since a certain oak version the leas check mode is STRICT, the
other two enum should not be used (LENIENT e DISABLED)
could someone explain me what's happening when I see in logs this stacktrace:
2024.10.14 10:45:34.439 - *ERROR* [DocumentNodeStore lease update thread (1)]
o.a.j.o.p.document.ClusterNodeInfo: This oak instance failed to update the
lease in time and can therefore no longer access this DocumentNodeStore. (since
2024-10-14T08:46:58.088Z) (leaseExpired in ClusterNodeInfo.java, line 1361)
2024.10.14 10:45:34.439 - *WARN * [DocumentNodeStore lease update thread (1)]
o.a.j.o.p.document.DocumentNodeStore: Background operation failed:
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: This oak
instance failed to update the lease in time and can therefore no longer access
this DocumentNodeStore. (since 2024-10-14T08:46:58.088Z) (run in
DocumentNodeStore.java, line 3733)
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: This oak
instance failed to update the lease in time and can therefore no longer access
this DocumentNodeStore. (since 2024-10-14T08:46:58.088Z)
at
org.apache.jackrabbit.oak.plugins.document.ClusterNodeInfo.leaseExpired(ClusterNodeInfo.java:1363)
at
org.apache.jackrabbit.oak.plugins.document.ClusterNodeInfo.renewLease(ClusterNodeInfo.java:968)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore.renewClusterIdLease(DocumentNodeStore.java:2441)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore$BackgroundLeaseUpdate.execute(DocumentNodeStore.java:3908)
at
org.apache.jackrabbit.oak.plugins.document.DocumentNodeStore$NodeStoreTask.run(DocumentNodeStore.java:3725)
at java.base/java.lang.Thread.run(Thread.java:840)
2024.10.14 10:45:34.626 - *ERROR* [DocumentNodeStore lease update thread (1)]
o.a.j.o.p.document.ClusterNodeInfo: This oak instance failed to update the
lease in time and can therefore no longer access this DocumentNodeStore. (since
2024-10-14T08:46:46.175Z) (leaseExpired in ClusterNodeInfo.java, line 1361)
2024.10.14 10:45:34.626 - *WARN * [DocumentNodeStore lease update thread (1)]
o.a.j.o.p.document.DocumentNodeStore: Background operation failed:
org.apache.jackrabbit.oak.plugins.document.DocumentStoreException: This oak
instance failed to update the lease in time and can therefore no longer access
this DocumentNodeStore. (since 2024-10-14T08:46:46.175Z) (run in
DocumentNodeStore.java, line 3733)
Thanks
Cordiali saluti / Best regards,
Raffaele Gambelli
Senior Java Developer
E raffaele.gambe...@cegeka.com<mailto:raffaele.gambe...@cegeka.com>
[CEGEKA] Via Ettore Cristoni, 84
IT-40033 Bologna (IT),Italy
T +39 02 2544271
WWW.CEGEKA.COM<https://www.cegeka.com>
[https://2655225.fs1.hubspotusercontent-na1.net/hubfs/2655225/0.0%20Cegeka%20(new)/1.%20Visuals/Email%20Signatures/Annual_Report_Visuals_2023_Email%20Banner%201.png]<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
Dichiarazione di
Riservatezza<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
Le informazioni contenute nella mail sono riservate. Se si rende conto di non essere il
destinatario corretto della mail, la preghiamo di segnalare l'errore al mittente e di
cancellare immediatamente il messaggio. L’utilizzo improprio di informazioni riservate può
comportare
sanzioni.<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
Protezione dei dati
personali<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
La informiamo che i suoi dati saranno trattati da Cegeka nel rispetto delle disposizioni di legge
applicabili (D. Lgs 196/2003 e Regolamento UE 679/2016). Per maggiori dettagli può consultare le
nostre informative privacy al link
<https://www.cegeka.com/en/annual-report-2023?utm_campaign=[EN]%20-%20Annual%20Report%202023&utm_source=email%20signature%20banner&utm_medium=email%20signature%20banner%20annual%20report%202023>
https://www.cegeka.com/it/informazioni-sulla-privacy.
<https://www.cegeka.com/it/informazioni-sulla-privacy>
