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
While testing #18701 I ran into a weird bug in evaluation GC for evaluations created for max-disconnect-timeout. After purging a job and running nomad system gc, I expect to find no more evaluations for the job. But the evaluation for max-disconnect-timeout still exists:
$ nomad eval list
ID Priority Triggered By Job ID Namespace Node ID Status Placement Failures
ba6f9a5d 50 max-disconnect-timeout httpd default <none> pending false
The text was updated successfully, but these errors were encountered:
I'm going to lock this issue because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
While testing #18701 I ran into a weird bug in evaluation GC for evaluations created for
max-disconnect-timeout
. After purging a job and runningnomad system gc
, I expect to find no more evaluations for the job. But the evaluation formax-disconnect-timeout
still exists:The text was updated successfully, but these errors were encountered: