[ https://issues.apache.org/jira/browse/AIRAVATA-2884?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831956#comment-16831956 ]
Dimuthu Upeksha commented on AIRAVATA-2884: ------------------------------------------- Fixed in new stack. Fixed inĀ [https://github.com/apache/airavata/commit/27eb5129e76dd8d0be7992a8c6b099314d1f5b7e] This occurred due to the bug in task creation logic where different tasks are getting same id and they eventually getting stacked up in helix queues > Unusual delay in helix job submission > ------------------------------------- > > Key: AIRAVATA-2884 > URL: https://issues.apache.org/jira/browse/AIRAVATA-2884 > Project: Airavata > Issue Type: Bug > Components: helix implementation > Affects Versions: 0.18 > Environment: https://staging.seagrid.org > Reporter: Eroma > Assignee: Dimuthu Upeksha > Priority: Major > Fix For: 0.18 > > Attachments: Screen Shot 2018-09-25 at 2.03.59 PM.png > > > # Unusual delay in job submission from Helix. > # The job submission happened after 8, 10, etc minutes from the experiment > creation. > # Some of the IDs to check > ## SLM001-Gaussian-Carbonate:9_3d5f55c2-c3bf-47f2-939a-5c35585f12bb > ## SLM001-NEK5000-BR2:9_51ba9624-0db9-4e07-8efc-8d224a71081e > # There are some which are create long time ago and the job is not submitted > ## SLM001-NEK5000-BR2:9_08ccf14f-34d9-468c-ac9f-6ffe434cbef7 > ## SLM001-NEK5000-BR2:8_cff5e293-4a84-4835-bbce-fce10acaa254 -- This message was sent by Atlassian JIRA (v7.6.3#76005)