[
https://issues.apache.org/jira/browse/IGNITE-8749?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16516531#comment-16516531
]
ASF GitHub Bot commented on IGNITE-8749:
----------------------------------------
GitHub user x-kreator opened a pull request:
https://github.com/apache/ignite/pull/4220
IGNITE-8749: storage error handling fix.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/x-kreator/ignite ignite-8749-fix
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4220.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #4220
----
commit cfdfd8a60c3964e298573d4baf0c2ccd223531da
Author: Dmitriy Sorokin <d.w.sorokin@...>
Date: 2018-06-19T00:51:09Z
IGNITE-8749: storage error handling fix.
----
> Exception for "no space left" situation should be propagated to FailureHandler
> ------------------------------------------------------------------------------
>
> Key: IGNITE-8749
> URL: https://issues.apache.org/jira/browse/IGNITE-8749
> Project: Ignite
> Issue Type: Improvement
> Components: persistence
> Reporter: Sergey Chugunov
> Assignee: Dmitriy Sorokin
> Priority: Major
> Fix For: 2.6
>
>
> For now if "no space left" situation is detected in
> FileWriteAheadLogManager#formatFile method and corresponding exception is
> thrown the exception doesn't get propagated to FailureHandler and node
> continues working.
> As "no space left" is a critical situation, corresponding exception should be
> propagated to handler to make necessary actions.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
