beam-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ahmet Altay (JIRA)" <>
Subject [jira] [Commented] (BEAM-1986) Job ALREADY_EXISTS in post commit
Date Tue, 18 Apr 2017 04:43:41 GMT


Ahmet Altay commented on BEAM-1986:

Yes, they are running in parallel. The current auto generated job id have seconds in it, why
would a 1-second delay would not fix the issue?

> Job ALREADY_EXISTS in post commit
> ---------------------------------
>                 Key: BEAM-1986
>                 URL:
>             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?
> 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

View raw message