[
https://issues.apache.org/jira/browse/IGNITE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16527489#comment-16527489
]
Alexey Goncharuk commented on IGNITE-8203:
------------------------------------------
[~alex_pl], I have one extra concern :)
Can you please check if the closed channel will keep throwing
{{ClosedByInterruptException}} on all further accesses? Consider the following
scenario:
1) Thread A attempts to read a file, the thread is interrupted, a correct
exception is thrown.
2) Thread A unwinds the stack to handle interruption and releases read lock
3) Thread B attempts to read the same file. If subsequent access results with a
plain IO exception, then thread B will not attempt to reopen the file and will
shut down the node
> Interrupting task can cause node fail with PersistenceStorageIOException.
> --------------------------------------------------------------------------
>
> Key: IGNITE-8203
> URL: https://issues.apache.org/jira/browse/IGNITE-8203
> Project: Ignite
> Issue Type: Bug
> Components: persistence
> Affects Versions: 2.4
> Reporter: Ivan Daschinskiy
> Assignee: Aleksey Plekhanov
> Priority: Major
> Fix For: 2.7
>
> Attachments: GridFailNodesOnCanceledTaskTest.java
>
>
> Interrupting task with simple cache operations (i.e. get, put) can cause
> PersistenceStorageIOException. Main cause of this failure is lack of proper
> handling InterruptedException in FilePageStore.init() etc. This cause a throw
> of ClosedByInterruptException by FileChannel.write() and so on.
> PersistenceStorageIOException is a critical failure and typically makes a
> node to stop. As a workaround, I would suggest to enable AsyncFileIO by
> default until the fix was available.
> A reproducer is attached.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
