[jira] [Resolved] (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:all-tabpanel ]

Michael Dürig resolved OAK-2405.
--------------------------------
    Resolution: Fixed

Fixed at http://svn.apache.org/viewvc?rev=1747254&view=rev

With these changes a {{SNFE}} will cause logging of additional information (if available) regarding the gc cycles that removed it:

{code}
Segment not found: 7e1a21a5-b74a-4688-a506-5c35ebc89d0b. 
SegmentId age=759ms,gc-count=3,timestamp=1465309323368,gc-status=success,store-generation=2,reclaim-predicate=(generation<=1)
{code}


> 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)