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

ASF GitHub Bot commented on IGNITE-8749:
----------------------------------------

GitHub user x-kreator opened a pull request:

    https://github.com/apache/ignite/pull/4216

    IGNITE-8749: after-merge code formatting.

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/x-kreator/ignite ignite-8749-fmt

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/ignite/pull/4216.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 #4216
    
----
commit c76f8994b7716f0960d82c2e94db9ea859c0e79e
Author: Dmitriy Sorokin <d.w.sorokin@...>
Date:   2018-06-18T12:58:26Z

    IGNITE-8749: after-merge code formatting.

----


> 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)

Reply via email to