[
https://issues.apache.org/jira/browse/BEAM-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Beam JIRA Bot updated BEAM-1986:
--------------------------------
Labels: (was: stale-assigned)
> 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-core
> Reporter: Ahmet Altay
> Priority: P3
>
> 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
(v8.3.4#803005)
