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
The document states that the distinct_hosts attribute of the constraints object should be a boolean:
# Define a job called my-servicejob"consul" {
# Job should run in the US regionregion="global"# Spread tasks between us-west-1 and us-east-1datacenters=["dc1"]
# run this job globallytype="system"# Rolling updates should be sequentialupdate {
stagger="30s"max_parallel=1
}
constraint{
distinct_hosts=true
}
group"consul-server" {
...
}
}
@F21 It looks like we are assuming that the bool value true/false for this constraint is in quotes. so distinct_hosts="true" works.
cc/ @dadgar@cbednarski Thoughts about the UX? I think the value that we get from the hcl parser is of type interface{} It might be nice for us to not treat the value as a string. I can have a PR going for this.
Adds metrics suggested in hashicorp#488, to record the percentage of time the
main and FSM goroutines are busy with work vs available to accept new
work, to give operators an idea of how close they are to hitting
capacity limits.
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.
The document states that the
distinct_hosts
attribute of theconstraints
object should be a boolean:However, if I set it to
true
, nomad panics:The text was updated successfully, but these errors were encountered: