-
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
Nomad doesn't cleanup down nodes after gc time #1245
Comments
Hey, If you run |
Can you also paste server logs of the normal periodic gc. The lines should look like:
Same for node and job |
my cmd output
Finally we restart nomad with debug log output, so get follow logs
so two times in a row doesn't help. То collect normal gc, we need some time |
Can you also run |
Also we publish our normal gc launch, as promise before:
|
The PR I just submitted should fix this! |
But how fix this with nomad 0.3.2? Any workaround? Or we must upgrade to last master ? |
You can not with 0.3.2. I would wait for 0.4 which will be out soon. This will have no performance impact as the object is very light weight. |
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
0.3.2
Operating system and Environment details
Linux consulnomad01 3.13.0-74-generic #118-Ubuntu SMP Thu Dec 17 22:52:10 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
in amazon aws
Issue
We have some down node which doesn't removed after gc time.
Nodes
Present in list more than 1 day
As mention in https://groups.google.com/forum/#!topic/nomad-tool/oQFPQSNrpxU, we provide follow info, for node bc9ffe4e(full ID bc9ffe4e-2331-9a01-191f-6b54f0d0e083) which present in list alredy 5 days
a). One of the node object which should be down
b). The allocation objects(atleast one) which is associated with the down node. [/v1/node//allocations]
c). The job object. [/v1/job/]
The text was updated successfully, but these errors were encountered: