[
https://issues.apache.org/jira/browse/BEAM-1986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17132426#comment-17132426
]
Beam JIRA Bot commented on BEAM-1986:
-------------------------------------
This issue is assigned but has not received an update in 30 days so it has been
labeled "stale-assigned". If you are still working on the issue, please give an
update and remove the label. If you are no longer working on the issue, please
unassign so someone else may work on it. In 7 days the issue will be
automatically unassigned.
> 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
> Assignee: Mark Liu
> Priority: P3
> Labels: stale-assigned
>
> 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)
