[ https://issues.apache.org/jira/browse/OAK-9601?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17430544#comment-17430544 ]
Stefan Egli commented on OAK-9601: ---------------------------------- * [PR created|https://github.com/apache/jackrabbit-oak/pull/394] > Refine logging to help detect dangling previous document pointers > ----------------------------------------------------------------- > > Key: OAK-9601 > URL: https://issues.apache.org/jira/browse/OAK-9601 > Project: Jackrabbit Oak > Issue Type: Task > Components: documentmk > Affects Versions: 1.40.0 > Reporter: Stefan Egli > Assignee: Stefan Egli > Priority: Minor > Fix For: 1.42.0 > > > The log warns similar to the below pattern occur rather regularly: > {noformat} > org.apache.jackrabbit.oak.plugins.document.NodeDocument Document with > previous revisions not found: 3:p/:async/r1795b3e463c-0-2/0 > {noformat} > While the root cause is not yet clear, it is likely that this is "only a > dangling pointer". > There were previous cases where something similar occurred: OAK-2377 (also > see the referenced OAK-1791) > In fact, in OAK-2377 the log has been lowered to debug but in the remaining 2 > cases it is still at warn: NodeDocument.getPreviousDoc and getPreviousDocs. > This ticket here is about 2 things: > * lowering the frequency of logging that warn, since it can flood log files > if it applies to a frequently read document > * add some more details to a suspect root cause for further analysis. -- This message was sent by Atlassian Jira (v8.3.4#803005)