Skip to content
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 node gc question #1215

Closed
sheweichun opened this issue May 30, 2016 · 6 comments
Closed

nomad node gc question #1215

sheweichun opened this issue May 30, 2016 · 6 comments

Comments

@sheweichun
Copy link

[question]

Nomad version

Nomad v0.3.2

Operating system and Environment details

Linux 3.10.0-229.el7.x86_64 #1 SMP Fri Mar 6 11:36:42 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux

how can I set nomad node gc strategy? after a scheduled job was finished some time,I can't find it,I event don't know whether it works.can I set gc interval longger? where to configure it?

@diptanu
Copy link
Contributor

diptanu commented May 30, 2016

@sheweichun Nomad GCs allocation after four hours. Are you trying to inspect the state of the job after four hours?

@sheweichun
Copy link
Author

I found in that I can set node_gc_threshold in server.hcl,but it didn't working!
My job is running at 4:00am every day,when I came to company,I even didn't know whether they had runned,even I couldn't check their log files

@dadgar
Copy link
Contributor

dadgar commented May 31, 2016

Hey, there may be a bug with the node GC at the moment. I will be looking
into it shortly.

On Mon, May 30, 2016 at 7:58 PM, sheweichun notifications@github.com
wrote:

I found in that I can set node_gc_threshold in server.hcl,but it didn't
working!
My job is running at 4:00am every day,when I came to company,I even didn't
know whether they had runned,even I couldn't check their log files


You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
#1215 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AA_9asSThlB83M0xQ-aC0WMMO-5A8G4Kks5qG6PNgaJpZM4IpdWd
.

@dadgar
Copy link
Contributor

dadgar commented Jun 3, 2016

Hey,

Sorry I misread this issue. Nomad stores everything in-memory and as such can not keep an unbounded history of allocations. We have blocking queries which allow you to pull for changes to allocations. This can be used to ingest the state changes and build your own long term storage solution.

This is not something we are tackling right now

@dadgar dadgar closed this as completed Jun 3, 2016
@hgontijo
Copy link
Contributor

hgontijo commented Aug 4, 2016

@diptanu is the GC executed every 4 hours the same as /v1/system/gc ?

@github-actions
Copy link

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.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Dec 20, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants