You are viewing a plain text version of this content. The canonical link for it is here.

Posted to oak-issues@jackrabbit.apache.org by "Michael Dürig (JIRA)" <ji...@apache.org> on 2015/03/02 12:55:04 UTC

[jira] [Resolved] (OAK-2407) Auto-refresh sessions on revision gc

     [ https://issues.apache.org/jira/browse/OAK-2407?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Dürig resolved OAK-2407.
--------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: 1.0.13)
                   1.0.12

Fixed in the 1.0 branch at http://svn.apache.org/r1663274

> Auto-refresh sessions on revision gc
> ------------------------------------
>
>                 Key: OAK-2407
>                 URL: https://issues.apache.org/jira/browse/OAK-2407
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: segmentmk
>            Reporter: Michael Dürig
>            Assignee: Michael Dürig
>              Labels: gc
>             Fix For: 1.2, 1.0.12
>
>
> The approach to revision garbage collection taken in OAK-2192 assumes that long running background sessions call refresh once they become active again. Incidentally this is true as such background sessions usually are admin sessions and those are always auto-refreshed on access (see OAK-88, OAK-803, and OAK-960). However as soon as we move away from admin sessions this might not be true any more and we might start seeing {{SegmentNotFoundException}} s unless the user explicitly refreshes the session. 
> To prevent this we should make all sessions auto refresh once revision gc runs. 



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