For now, if I use setLeaseCheckMode(LeaseCheckMode.DISABLED) in the document store, I should stop seeing that error, right?
El mar., 3 mar. 2020 a las 12:38, jorgeeflorez . (< [email protected]>) escribió: > It is done: https://issues.apache.org/jira/browse/OAK-8935 > > El mar., 3 mar. 2020 a las 10:06, Julian Reschke (<[email protected]>) > escribió: > >> On 03.03.2020 15:48, jorgeeflorez . wrote: >> >> >> >> First step would be to upgrade to 1.24.0 >> >> >> > We just upgraded from 1.5 last year. I guess I will not find much >> trouble >> > upgrading from 1.12, right? >> >> 1.5 was an unstable branch, you shouldn't use that in production anyway. >> >> 1.24.0 has replaced 1.12.0 as latest stable release. >> >> > the output of "ipconfig -a" for that machine would be helpful. >> >> >> > >> > Here is the output, MAC changed and IP addresses hidden/changed. >> > >> > docker0 Link encap:Ethernet HWaddr 02:4E:C5:4B:C5:E5 >> > inet addr:xxx.xx.x.x Bcast:xxx.xxx.xxx.xxx Mask:xxx.xxx.x.x >> > UP BROADCAST MULTICAST MTU:1500 Metric:1 >> > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:0 >> > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) >> > >> > eth0 Link encap:Ethernet HWaddr 06:C5:FB:F8:CF:C7 >> > inet addr:xxx.xx.xx.xx Bcast:xxx.xxx.xxx.xxx >> Mask:xxx.xxx.xxx.xx >> > inet6 addr: fe80::4c8:fafd:fec1:cfc0/64 Scope:Link >> > UP BROADCAST RUNNING MULTICAST MTU:9001 Metric:1 >> > RX packets:2694 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:2721 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:1000 >> > RX bytes:306659 (299.4 KiB) TX bytes:343151 (335.1 KiB) >> > >> > lo Link encap:Local Loopback >> > inet addr:127.0.0.1 Mask:255.0.0.0 >> > inet6 addr: ::1/128 Scope:Host >> > UP LOOPBACK RUNNING MTU:65536 Metric:1 >> > RX packets:35 errors:0 dropped:0 overruns:0 frame:0 >> > TX packets:35 errors:0 dropped:0 overruns:0 carrier:0 >> > collisions:0 txqueuelen:1000 >> > RX bytes:81477 (79.5 KiB) TX bytes:81477 (79.5 KiB) >> > ... >> >> Ack. So yes, it probably would be good to extend the hack that we >> introduced in https://issues.apache.org/jira/browse/OAK-3885 for that >> interface. >> >> Can you open a Jira ticket for this? >> >> Best regards, Julian >> >
