You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Dmitriy Setrakyan (JIRA)" <ji...@apache.org> on 2015/09/08 06:00:47 UTC

[jira] [Updated] (IGNITE-1384) Compute job ids duplication

     [ https://issues.apache.org/jira/browse/IGNITE-1384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dmitriy Setrakyan updated IGNITE-1384:
--------------------------------------
    Labels: user-request  (was: )

> Compute job ids duplication
> ---------------------------
>
>                 Key: IGNITE-1384
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1384
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Sidorov
>              Labels: user-request
>
> Configure custom CollisionSpi with any implemenation which keeps waiting jobs list not empty. Execute considerable amount of tasks (e.g. 10000) from 2 or more nodes with jobs mapped to one node.
> Error occurs on mapped node: "Received computation request with duplicate job ID (could be network malfunction, source node may hang if task timeout was not set)"
> Reason: TaskGridWorker:processMappedJobs generates job ids as following: IgniteUuid jobId = IgniteUuid.fromUuid(node.id()); 
> where node.id() is identifier of node the job is mapped to. So parallel generation of job ids on different nodes leads to ids duplication.
> Possible solution: use node.id() of local node in job id generation.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)