[jira] [Commented] (OAK-2405) Monitoring to track old NodeStates

["Michael Dürig (JIRA)" <ji...@apache.org>]

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

Michael Dürig commented on OAK-2405:
------------------------------------

After OAK-3348 introduced generation based cleanup I think there is not much left to do here except for annotating segment ids of gc'ed segments with the gc information should they still be tracked via the segment tracker. See my [comment | https://issues.apache.org/jira/browse/OAK-4285?focusedCommentId=15296344&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15296344] on OAK-4285 to that respect. 



> Monitoring to track old NodeStates
> ----------------------------------
>
>                 Key: OAK-2405
>                 URL: https://issues.apache.org/jira/browse/OAK-2405
>             Project: Jackrabbit Oak
>          Issue Type: Sub-task
>          Components: segment-tar
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: gc, monitoring, tooling
>             Fix For: 1.6
>
>
> We should add some monitoring that allows us to track "old" node states, which potentially block revision gc. 
> Possible approaches:
> * Add monitoring too old revisions (root node states) along with the stack traces from where they have been acquired.
> * Include RecordId of root node state in the {{SessionMBean}}.
> * Add additional tooling on top of the {{SessionMBean}} to make it easier to make sense of the wealth of information provided. 



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