You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@asterixdb.apache.org by "Murtadha Hubail (JIRA)" <ji...@apache.org> on 2017/12/24 01:53:00 UTC
[jira] [Assigned] (ASTERIXDB-1464) Dealing with
InterruptedException in LogManager
[ https://issues.apache.org/jira/browse/ASTERIXDB-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Murtadha Hubail reassigned ASTERIXDB-1464:
------------------------------------------
Assignee: Murtadha Hubail (was: Michael Blow)
> Dealing with InterruptedException in LogManager
> -----------------------------------------------
>
> Key: ASTERIXDB-1464
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1464
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: TX - Transactions
> Reporter: Murtadha Hubail
> Assignee: Murtadha Hubail
>
> Currently, most InterruptedExceptions are ignored in LogManager. This could lead to jobs not aborted in a timely manner when an interrupt is received from the CC. The current behavior on each InterruptedException should be defined and the exceptions should be propagated accordingly.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)