tephra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (TEPHRA-242) Transaction Service sometimes does not shutdown
Date Thu, 31 Aug 2017 22:43:02 GMT

    [ https://issues.apache.org/jira/browse/TEPHRA-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16149722#comment-16149722

ASF GitHub Bot commented on TEPHRA-242:

GitHub user anew opened a pull request:


    [TEPHRA-242] Ensure Pruning Service shuts down

    Shutdown the pruning service before the tx server, to ensure it shuts down even if tx
server shutdown is interrupted. 

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/anew/incubator-tephra tephra-242

Alternatively you can review and apply these changes as the patch at:


To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #49
commit 944509fc25167fc52815673b01a7b03295628711
Author: anew <anew@apache.org>
Date:   2017-08-31T22:41:10Z

    [TEPHRA-242] Ensure Pruning Service shuts down


> Transaction Service sometimes does not shutdown
> -----------------------------------------------
>                 Key: TEPHRA-242
>                 URL: https://issues.apache.org/jira/browse/TEPHRA-242
>             Project: Tephra
>          Issue Type: Bug
>          Components: manager
>    Affects Versions: 0.12.0-incubating
>            Reporter: Andreas Neumann
>            Assignee: Andreas Neumann
>             Fix For: 0.13.0-incubating
> If shutting down encounters an exception (for example, OutOfMemory), it can happen that
the process does not exit. We have observed this after an NPE from DFS (closing the transaction
log), the process stayed alive and the\ prune thread (executor) was not shut down. It was
not clear why the process stayed alive, but it would certainly help to handle exceptions better
in the shutdown sequence. 

This message was sent by Atlassian JIRA

View raw message