[
https://issues.apache.org/jira/browse/IGNITE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16276887#comment-16276887
]
Andrew Mashenkov commented on IGNITE-1267:
------------------------------------------
[~sboikov],
I've remove EVT_NODE_JOINED from listener.
Job stealing is happened on EVT_NODE_METRICS_UPDATED as it was before, but now
newly joined node is able to steal jobs.
Triggering stealing on EVT_NODE_JOINED has no effect. Seems, there is a race in
event handling.
Let's merge this to master if you don't mind as it looks like almost fixed and
create a ticket for triggering job stealing on EVT_NODE_JOINED event?
> JobStealingCollisionSpi never sends jobs to a node that joined after task was
> executed
> --------------------------------------------------------------------------------------
>
> Key: IGNITE-1267
> URL: https://issues.apache.org/jira/browse/IGNITE-1267
> Project: Ignite
> Issue Type: Bug
> Components: compute
> Affects Versions: 1.1.4
> Reporter: Valentin Kulichenko
> Assignee: Andrew Mashenkov
> Labels: user-request
>
> Corresponding user thread (contains detailed description of the scenario that
> doesn't work):
> http://apache-ignite-users.70518.x6.nabble.com/Dynamic-ComputeTask-distribution-with-new-nodes-td997.html
> Essentially, {{JobStealingCollisionSpi}} always skips jobs that are not in
> task topology (see line 713). Task topology is static and created when task
> is executed, so newly joined node can't steal jobs. I think it should be able
> to do this if it satisfies initial cluster group predicate.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
