jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vikas Saurabh (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (OAK-4623) Log more information when null DocumentNodeState is read for a child while fetching children
Date Mon, 01 Aug 2016 09:44:20 GMT

    [ https://issues.apache.org/jira/browse/OAK-4623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401774#comment-15401774
] 

Vikas Saurabh commented on OAK-4623:
------------------------------------

Actually, thinking further, I think we already log the useful bits even now - we get {{readRevision}}
at which the child was listed but its {{DocumentNodeState}} turned out to be null.

We can get more data by may be logging parent's node state too but I wonder what else, other
than read revision, can we extract out of it.

Ping [~chetanm], [~mreutegg] for ideas.

> 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.6
>
>
> {{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.4#6332)

Mime
View raw message