You are viewing a plain text version of this content. The canonical link for it is here.
Posted to github@beam.apache.org by GitBox <gi...@apache.org> on 2022/06/03 17:13:13 UTC

[GitHub] [beam] kennknowles opened a new issue, #18255: Job ALREADY_EXISTS in post commit

kennknowles opened a new issue, #18255:
URL: https://github.com/apache/beam/issues/18255

   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. 
   
   Imported from Jira [BEAM-1986](https://issues.apache.org/jira/browse/BEAM-1986). Original Jira may contain additional context.
   Reported by: altay.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@beam.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org