You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ignite.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2018/04/02 08:07:00 UTC

[jira] [Commented] (IGNITE-8069) IgniteOutOfMemoryException should be handled accordingly to provided failure handler

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

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

GitHub user alex-plekhanov opened a pull request:

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

    IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly …

    …to provided failure handler

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

    $ git pull https://github.com/alex-plekhanov/ignite ignite-8069

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

    https://github.com/apache/ignite/pull/3729.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 #3729
    
----
commit fddeea5c509939e29dc126197e29cdcbc14bc33d
Author: Aleksey Plekhanov <pl...@...>
Date:   2018-04-02T07:35:25Z

    IGNITE-8069 IgniteOutOfMemoryException should be handled accordingly to provided failure handler

----


> IgniteOutOfMemoryException should be handled accordingly to provided failure handler
> ------------------------------------------------------------------------------------
>
>                 Key: IGNITE-8069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-8069
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Andrey Gura
>            Assignee: Aleksey Plekhanov
>            Priority: Major
>              Labels: iep-14
>             Fix For: 2.5
>
>
> {{IgniteOutOfMemoryException}} should be handled accordingly to provided failure handler.
> There are a couple of places where this exception can be thrown. Need to find a common place(s) where this exception could be handled.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)