You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Julian Reschke (JIRA)" <ji...@apache.org> on 2016/06/30 16:55:10 UTC

[jira] [Created] (OAK-4526) LeaseUpdateThread vs long-running GC

Julian Reschke created OAK-4526:
-----------------------------------

             Summary: LeaseUpdateThread vs long-running GC
                 Key: OAK-4526
                 URL: https://issues.apache.org/jira/browse/OAK-4526
             Project: Jackrabbit Oak
          Issue Type: Improvement
          Components: documentmk
            Reporter: Julian Reschke


We've seen cases where OAK was running with a huge heap (80GB) and GC causes the system to freeze long enough to cause the lease update to fail.

In cases like these, better diagnostics could be helpful. For instance, the lease update thread could log (warn?) when the timestamp of the previous run of the thread is too far in the past.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)