[ 
https://issues.apache.org/jira/browse/IGNITE-8203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16504488#comment-16504488
 ] 

Ivan Daschinskiy edited comment on IGNITE-8203 at 6/7/18 10:02 AM:
-------------------------------------------------------------------

I'm a little bit stuck in fixing this issue. Currently, I fixed initialization 
of pagestore and my reproducer passes. But, after discussion with Alexey, I 
realized that this is not enough. Read and write are unfortunatelly still 
vulnerable to interruptions. Unfortunatelly, my reproducer doesn't touch these 
situations


was (Author: ivandasch):
I'm a little bit stuck in fixing this issue. Currently, I fixed initialization 
and my reproducer passes. But, after discussion with Alexey, I realized that 
this is not enough. Read and write are unfortunatelly still vulnerable to this 
issue. 

> 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: Ivan Daschinskiy
>            Priority: Major
>             Fix For: 2.6
>
>         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)

Reply via email to