[
https://issues.apache.org/jira/browse/IGNITE-8813?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515602#comment-16515602
]
ASF GitHub Bot commented on IGNITE-8813:
----------------------------------------
GitHub user dkarachentsev opened a pull request:
https://github.com/apache/ignite/pull/4213
IGNITE-8813 - Add ComputeJobResultPolicy to JobEvent
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/gridgain/apache-ignite ignite-8813
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/ignite/pull/4213.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 #4213
----
commit c02a0699bc35ffb5e00827b7f07eaddce22d088b
Author: dkarachentsev <dkarachentsev@...>
Date: 2018-06-18T11:23:53Z
IGNITE-8813 - Add ComputeJobResultPolicy to JobEvent
----
> Add ComputeJobResultPolicy to JobEvent
> --------------------------------------
>
> Key: IGNITE-8813
> URL: https://issues.apache.org/jira/browse/IGNITE-8813
> Project: Ignite
> Issue Type: Improvement
> Components: compute
> Affects Versions: 2.5
> Reporter: Dmitry Karachentsev
> Assignee: Dmitry Karachentsev
> Priority: Major
> Fix For: 2.6
>
>
> There is no way to determine on node-mapper what action would be performed on
> EVT_JOB_RESULTED event, as got result could return different policies: WAIT,
> REDUCE, FAILOVER. This knowledge might be critical for user if it relies on
> events, and, for instance, he need to know if EVT_JOB_RESULTED is final
> event, or it will be failed over and will be fired again.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
