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 "Thomas Mueller (JIRA)" <ji...@apache.org> on 2015/11/27 14:12:11 UTC

[jira] [Commented] (OAK-3303) FileStore flush thread can get stuck

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

Thomas Mueller commented on OAK-3303:
-------------------------------------

An alternative explanation of the stuck thread: currently, the priority is set as follows: "setPriority(MIN_PRIORITY)". As it's used with a long delay anyway, I would probably not set the priority, but use the default. 

>  stuck for a while

Do you remember if the thread name was just "TarMK ... thread [...]", or that plus "active since" or plus "avg ... max ..."? If the thread name did contain "active since" or "avg ... max ...", then interval was not 0. But, to rule out the "interval" is not yet set, maybe the thread name could be set before the first iteration.


> FileStore flush thread can get stuck
> ------------------------------------
>
>                 Key: OAK-3303
>                 URL: https://issues.apache.org/jira/browse/OAK-3303
>             Project: Jackrabbit Oak
>          Issue Type: Bug
>          Components: segmentmk
>            Reporter: Alex Parvulescu
>            Assignee: Alex Parvulescu
>             Fix For: 1.3.12
>
>
> In some very rare circumstances the flush thread was seen as possibly stuck for a while following a restart of the system. This results in data loss on restart (the system will roll back to the latest persisted revision on restart), and worse off there's no way of extracting the latest head revision using the tar files, so recovery is not (yet) possible.



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