-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fingerprinting Nomad Clients (on restart) on Windows and ESXI hosts can far exceed the heartbeat #10761
Comments
Thanks @idrennanvmware. I think the approach to get that fixed in the upstream library is the right one. Marking this as accepted and once that lands we'll get it in the next patch. |
Thanks to everyone for making this such a quick process! |
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. |
Nomad version
1.0.4
Operating system and Environment details
Windows
Issue
When restarting a Nomad agent on an ESXI host (vSphere) with a Windows VM, it can take over 15 seconds to fingerprint.
Right now we have manipulated the Heartbeat TTL settings to work around this, but it is not ideal. Unfortunately this issue causes all windows allocations to be "lost" during a Nomad agent restart which then causes other disruptions to our cluster(s)
Fix
@fredwangwang has submitted a PR to the underlaying library, here shirou/gopsutil#1088 and when/if this is merged we are requesting this get included in the next Nomad refresh
Thanks!
The text was updated successfully, but these errors were encountered: