Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Potential hanging job after execution completes #514

Closed
gschueler opened this issue Aug 19, 2013 · 0 comments
Closed

Potential hanging job after execution completes #514

gschueler opened this issue Aug 19, 2013 · 0 comments
Labels
bug
Milestone
1.6.1

Comments

@gschueler
Copy link
Member

If the DB write fails to update the job stats after execution is complete, the execution state may not get saved since it is modified in the same transaction.

  1. separate the changes into two separate transactions
  2. if job stat change fails, retry X times before skipping since it is not crucial
gschueler added a commit that referenced this issue Aug 19, 2013
@gschueler
Separate state changes for exec and job #514
1e285c2 
* Update execution state from ExecutionJob as a separate service method
* then update job stats, retry X times if a failure, and give up

Execution should not appear "hung" if simple duration stat update fails
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug
Projects
None yet
Milestone
1.6.1
Development

No branches or pull requests
1 participant
@gschueler