You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ignite.apache.org by "Denis Magda (JIRA)" <ji...@apache.org> on 2016/07/05 11:47:10 UTC
[jira] [Updated] (IGNITE-3426) Compute Engine: job ID is generated
in a non unique way
[ https://issues.apache.org/jira/browse/IGNITE-3426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Denis Magda updated IGNITE-3426:
--------------------------------
Assignee: Denis Magda
> 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)