jackrabbit-oak-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcel Reutegger (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (OAK-8521) Add shutdown hook for oak-run commands
Date Tue, 06 Aug 2019 13:07:00 GMT

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

Marcel Reutegger resolved OAK-8521.
       Resolution: Fixed
    Fix Version/s: 1.18.0

Applied a slightly modified patch to trunk: http://svn.apache.org/r1864518

Thanks for the contribution Vinod.

> Add shutdown hook for oak-run commands
> --------------------------------------
>                 Key: OAK-8521
>                 URL: https://issues.apache.org/jira/browse/OAK-8521
>             Project: Jackrabbit Oak
>          Issue Type: Improvement
>          Components: documentmk, run
>            Reporter: Vinod Holani
>            Assignee: Marcel Reutegger
>            Priority: Minor
>             Fix For: 1.18.0
>         Attachments: OAK-8521.patch
> Ensure there are shutdown hooks in place for the various oak-run commands that properly
stop the repository and release the clusterId.
> Many command construct a repository, then perform some operation and then shut down the
repository again. Shutting down the repository will release the clusterId change the state
of the clusterNodes entry back to inactive. In some cases commands execute for a longer period
of time and a user might kill the process. When this happens, the clusterId is not released
and stays in the active state with a lease that eventually expires. The command implementations
should be improved to register a JVM shutdown hook that ensures the repository is shut down,
even when the process is killed.

This message was sent by Atlassian JIRA

View raw message