ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yakov Zhdanov (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (IGNITE-1384) Compute job ids duplication
Date Fri, 29 Apr 2016 12:59:12 GMT

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

Yakov Zhdanov closed IGNITE-1384.

> Compute job ids duplication
> ---------------------------
>                 Key: IGNITE-1384
>                 URL: https://issues.apache.org/jira/browse/IGNITE-1384
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Sergey Sidorov
>            Assignee: Yakov Zhdanov
>              Labels: user-request
>             Fix For: 1.6
> 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

View raw message