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
After taking a closer look at this the issue we determined that currently Nomad does not check for differences in affinities or constraints when determining whether to do an inplace update or create a new allocation.
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.
Nomad version
v0.9.5 (1cbb2b9)
Operating system and Environment details
Debian GNU/Linux 10 (buster)
Issue
Node affinity stays in
Placement Metrics
after moving it out from the job spec.Reproduction steps
Testing Nomad cluster consists of single server and three client nodes, two of them have
meta.tier = hi
, the last one hasmeta.tier = lo
.Submitting the following job definition:
One node wins due to
node-affinity
(two of them match, because there are two nodes withmeta.tier = hi
):Now I decide to remove the
affinity
:Looks like it'll go away as expected:
But there are still two nodes with
node-affinity
equal to 1The text was updated successfully, but these errors were encountered: