Thanks. I'm using MongoDB, the DB is right on the machine, which seems reliable enough (and I see no database connection exceptions). File system seems like a good option for me, however the transparency and visibility of using MongoDB were the reasons of using it. It seems that the database connection must not be the issue here.
On Tue, Aug 1, 2017 at 6:51 PM, Julian Reschke <[email protected]> wrote: > On 2017-08-01 15:45, Mostafa Mahdieh wrote: > >> Hi, >> >> I'm using jackrabbit oak as the content repository of a document >> management >> system product. Currently there is no need to scale out, therefore I'm >> using jackrabbit oak in a single node environment. However, I'm >> experiencing issues related to clustering and lease time, such as the >> following exception which is appearing all over my tomcat logs: >> >> WARN: 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. >> >> After some research, It seems that there is no way to use jackrabbit oak >> forcing it to use a single node and not having any concerns related to >> clustering. >> ... >> > > Well, a single node is just a very small cluster :-). > > If you see the message above, apparently your connection to the > persistence (is it Mongo or RDB?) isn't reliable, or the DB itself is > flaky. The log files should show you more. > > That said, you can use Oak with filesytem-based persistence as well, in > which case this class of issues would go away (but then you'd need to > migrate the persistence if later you decide you need to scale to a real > cluster) > > Best regards, Julian > > -- Mostafa Mahdieh
