[
https://issues.apache.org/jira/browse/ASTERIXDB-1464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16311888#comment-16311888
]
ASF subversion and git services commented on ASTERIXDB-1464:
------------------------------------------------------------
Commit b4899c89da5d27bb6a586e75111868f65284d734 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=b4899c8 ]
[ASTERIXDB-1464][TX] Handle Interrupts in LogManager
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Properly handle interrupts on log page
and log file switch in LogManager.
- Propagate interrupts on transactor threads.
- Ignore interrupts while waiting for txn
commit/abort log to be flushed.
- Add test case for handling interrupts in
LogManager.
- Add test case for interrupting a txn waiting
for commit log.
Change-Id: I6936a60dc572e07f01baabc3f8af3bf88a58f661
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2248
Integration-Tests: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
Contrib: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
> 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)
