[
https://issues.apache.org/jira/browse/ASTERIXDB-2046?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16166500#comment-16166500
]
ASF subversion and git services commented on ASTERIXDB-2046:
------------------------------------------------------------
Commit 2e3c52015bfed6d6bed6c26124a3cf10b10864c5 in asterixdb's branch
refs/heads/master from [~mhubail]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=2e3c520 ]
[ASTERIXDB-2046][STO] Retry Reading a Page on ClosedChannelException
- user model changes: no
- storage format changes: no
- interface changes: no
Details:
- Currently when concurrent threads are reading from the same file
and one of them is interrupted, the file channel will be closed and
other threads will fail with AsynchronousCloseException if they were
reading or ClosedChannelException if they were about to read the file.
This change make the threads that were not interrupted retry the read
operation.
Change-Id: I4f9de9f51596314d17e4c6a4a58333e8fd6c03d1
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2005
Sonar-Qube: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Reviewed-by: abdullah alamoudi <bamou...@gmail.com>
Tested-by: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenk...@fulliautomatix.ics.uci.edu>
> Gracefully handle concurrent reads on ClosedByInterruptException
> ----------------------------------------------------------------
>
> Key: ASTERIXDB-2046
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-2046
> Project: Apache AsterixDB
> Issue Type: Improvement
> Reporter: Murtadha Hubail
>
> The fix in ASTERIXDB-2040 solves the issue of ClosedByInterruptException on
> an index file by opening the file channel again. However, the concurrent
> reads on the same file channels will fail when the exception is encountered
> as well. This needs to be handled so that the concurrent reads are either
> synchronized or retried after the file channel is opened again.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
