[
https://issues.apache.org/jira/browse/OAK-9321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17264253#comment-17264253
]
Andrew Khoury commented on OAK-9321:
------------------------------------
If a long running session is identified, it would make sense to log a WARN
message, at least the first time that session is identified as a long running
session. Maybe set a flag thereafter and log at DEBUG level.
> Oak sessions should be refreshed before tail compaction
> -------------------------------------------------------
>
> Key: OAK-9321
> URL: https://issues.apache.org/jira/browse/OAK-9321
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: jcr
> Affects Versions: 1.22.5
> Reporter: Jörg Hoh
> Priority: Major
>
> Although discouraged since forever, long running JCR sessions are still seen
> quite often in applications I see.
> One effect of these long running sessions is that in combination with tail
> compaction it can lead to SegmentNotFoundExceptions. These exceptions are not
> persistent, meaning that the storage layer is not affected. A restart will
> cause the SNFE to vanish until they appear again after some time.
> Of course fixing the long running sessions is definitely the right way to fix
> this problem, but it'S unlikely that it can be fixed easily in all cases.
> Therefor I would propose to have a workaround, which refreshes all open
> sessions (older than 1h?) before performing tail compaction. It would be
> great, if the sessions would be logged, which are refreshed, so it can serve
> as input for the fixing.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
