Mailing-List: contact issues-help@ignite.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@ignite.apache.org
Date: Tue, 5 Jul 2016 11:57:11 +0000 (UTC)
From: "Denis Magda (JIRA)" <jira@apache.org>
To: issues@ignite.apache.org
Message-ID: <JIRA.12986791.1467719183000.25286.1467719831185@Atlassian.JIRA>
In-Reply-To: <JIRA.12986791.1467719183000@Atlassian.JIRA>
References: <JIRA.12986791.1467719183000@Atlassian.JIRA> <JIRA.12986791.1467719183276@arcas>
Subject: [jira] [Comment Edited] (IGNITE-3426) Compute Engine: job ID is
 generated in a non unique way
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 05 Jul 2016 11:57:13 -0000


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

Denis Magda edited comment on IGNITE-3426 at 7/5/16 11:56 AM:
--------------------------------------------------------------

One liner fix. Job ID will be generated using this code 
{code}
IgniteUuid jobId = IgniteUuid.fromUuid(ctx.localNodeId());
{code}

Checking with TC.


was (Author: dmagda):
One liner fix. Job ID will be generated using this code {{            IgniteUuid jobId = IgniteUuid.fromUuid(ctx.localNodeId());
}}

Checking with TC.

> Compute Engine: job ID is generated in a non unique way
> -------------------------------------------------------
>
>                 Key: IGNITE-3426
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3426
>             Project: Ignite
>          Issue Type: Improvement
>            Reporter: Denis Magda
>            Assignee: Denis Magda
>
> Presently seems like new job IDs are generated in a way that is not guaranteed to be unique.
> Specifically, job IDs are generated in: 
> {code}
> IgniteUuid jobId = IgniteUuid.fromUuid(node.id());
> org/apache/ignite/internal/processors/task/GridTaskWorker.java:564)
> {code}
> fromUuid generates the new job ID using UUID passed to it + an AtomicInteger (who is always incremented). Since the UUID passed to it is the *destination node* and not the local node, in environments where the job submission is relatively even, the generated job ID might not be unique.
> Think that the UUID used there is supposed to be the local node UUID.
> Otherwise this can be a reason of the following exception
> {noformat}
>  "Jobs map already contains mapping for key" 
> {noformat}


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