[
https://issues.apache.org/jira/browse/OAK-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15956713#comment-15956713
]
Vikas Saurabh commented on OAK-4623:
------------------------------------
Just adding an explicit note as the fix of this issue has side-effects while
logging
-----
While the title of the issue is specific to adding log information - but the
way we produce that log explicitly reads remote data and update (potentially
incorrect) child node state. So, in case child node state cache was incorrect
while the listing was ok (likely case) then logging the information would also
fix the cached state.
----
> Log more information when null DocumentNodeState is read for a child while
> fetching children
> --------------------------------------------------------------------------------------------
>
> Key: OAK-4623
> URL: https://issues.apache.org/jira/browse/OAK-4623
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: documentmk
> Reporter: Vikas Saurabh
> Assignee: Vikas Saurabh
> Priority: Minor
> Fix For: 1.0.34, 1.2.19, 1.4.7, 1.5.9, 1.6.0
>
>
> {{DocumentNodeStore#getChildNodes}} validates node states of children in the
> returned iterator and throws exception if a child is read as {{null}}.
> This is clearly an unexpected case (although, it has been observed in running
> systems). The more probable cause for such a scenario would be to have
> inconsistent value in {{nodeChildrenCache}}. It'd be useful to log more
> information about cache state to help investigating such cases.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
