You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@beam.apache.org by "Ahmet Altay (JIRA)" <ji...@apache.org> on 2017/04/17 18:01:41 UTC

[jira] [Created] (BEAM-1986) Job ALREADY_EXISTS in post commit

Ahmet Altay created BEAM-1986:
---------------------------------

             Summary: Job ALREADY_EXISTS in post commit
                 Key: BEAM-1986
                 URL: https://issues.apache.org/jira/browse/BEAM-1986
             Project: Beam
          Issue Type: Bug
          Components: sdk-py
            Reporter: Ahmet Altay
            Assignee: Mark Liu
            Priority: Minor


I noticed a job failed with ALREDY_EXISTS error, a sign of same {{job_name}} auto generated twice. Could we add a 1 second delay to prevent things like this?

https://builds.apache.org/view/Beam/job/beam_PostCommit_Python_Verify/1877/consoleFull

cc: [~pabloem] Another perspective, would it make sense to add a small random component (e.g. 1-2 digits) to job name to reduce this issue? Or perhaps include ms resolution. 



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)