You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When deregistering a job, Nomad explicitly creates an Evaluation if the job doesn't exist. It's unclear why this is the case, and it seems a bit wasteful.
The behavior was introduced without much context in #981, and is masked as an improvement in the changelog.
It's unclear what the benefit of the behavior is. We speculate that it is bandaid around an deregistering atomicity bug, or to ensure idempotency of deregistration (e.g. re-deregister job should always succeed).
This lead to a discussion in #8435 (comment) as it complicated the handling of atomic job deregistration logic.
Investigate further and act accordingly.
The text was updated successfully, but these errors were encountered:
When deregistering a job, Nomad explicitly creates an Evaluation if the job doesn't exist. It's unclear why this is the case, and it seems a bit wasteful.
The behavior was introduced without much context in #981, and is masked as an improvement in the changelog.
It's unclear what the benefit of the behavior is. We speculate that it is bandaid around an deregistering atomicity bug, or to ensure idempotency of deregistration (e.g. re-deregister job should always succeed).
This lead to a discussion in #8435 (comment) as it complicated the handling of atomic job deregistration logic.
Investigate further and act accordingly.
The text was updated successfully, but these errors were encountered: