Control Nomad job restart due to Vault key update

Hi team,

Our Nomad jobs are getting restarted whenever a linked vault key is updated, which is the desired behaviour. I am looking for some info how can we better control the restarts. We have 8 instances in a job and if all 8 restart at the same time, we experience and outage for about 5-6 seconds (the time it takes for the allocs to restart).

Can the update or restart stanza be useful here? Asking as I could not find anything in the docs.

thanks.

1 Like

Hi @vikas.saroha,

The template.splay job specification option should help avoid this thundering heard problem.

Thanks,
jrasell and the Nomad team