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 "Mohammad (Jira)" <ji...@apache.org> on 2022/07/17 07:11:00 UTC
[jira] [Commented] (OAK-9842) Error in cluster node recovery: OutOfMemoryError GC overhead limit exceeded
[ https://issues.apache.org/jira/browse/OAK-9842?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17567573#comment-17567573 ]
Mohammad commented on OAK-9842:
-------------------------------
[~mreutegg] Would you please check this issue? As I checked you wrote most of these parts and now have this issue in production.
Thanks.
> Error in cluster node recovery: OutOfMemoryError GC overhead limit exceeded
> ---------------------------------------------------------------------------
>
> Key: OAK-9842
> URL: https://issues.apache.org/jira/browse/OAK-9842
> Project: Jackrabbit Oak
> Issue Type: Bug
> Affects Versions: 1.36.0
> Reporter: Mohammad
> Priority: Blocker
> Attachments: dominator-tree.jpg, dominator-tree.zip, histogram.zip, not yet visible - stacktrace.txt, recovery detailed - log.txt
>
>
> I have used jackrabbit oak on a large scale as a CMS module. In some write operation I got the OakMerge0004 (not yet visible) error. I have done some investigation before and found out this error will be solved with performing recovery on crashed clusterId. In all cases except the current state I have run the recovery and the problem was solved. But now I got
> {code:java}
> java.lang.OutOfMemoryError: GC overhead limit exceeded
> {code}
> Also I increased the Xmx to about 27GB but again I got the same error. I attached the report of the heap dump and detailed log. If any other information is needed please let me know.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)