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 "Chetan Mehrotra (JIRA)" <ji...@apache.org> on 2016/01/29 10:19:39 UTC

[jira] [Updated] (OAK-3952) BackgroundObserver close should wait for stop to be processed

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

Chetan Mehrotra updated OAK-3952:
---------------------------------
    Attachment: OAK-3952-v1.patch

[proposed patch|^OAK-3952-v1.patch] which makes use of a latch for close call to wait upon

> BackgroundObserver close should wait for stop to be processed
> -------------------------------------------------------------
>
>                 Key: OAK-3952
>                 URL: https://issues.apache.org/jira/browse/OAK-3952
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: core
>            Reporter: Chetan Mehrotra
>            Assignee: Chetan Mehrotra
>            Priority: Minor
>             Fix For: 1.4
>
>         Attachments: OAK-3952-v1.patch
>
>
> {{BackgroundObserver}} close method currently says that it does not wait for thread to finish. This can lead to situation when during shutdown the backing {{NodeStore}} goes away while the background thread is still busy with diff and that would lead to exceptions in the log.
> As being done in OAK-3923 the close call should wait for {{STOP}} signal to be processed before returning from close call.
> On side note we should also provide an option where the close call should wait for the queue to be processed instead of just silently clearing the queue which can lead to potential loss of important local events. Note that can happen for proper ordered shutdown!



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