Serf timeouts

[gregory-m]

Implanted serf reconnect and tombstone timeouts configuration.

Close #333

[dadgar]

Hey, I apologize for not looking into more detail when you filed the bug but I don't think we need to adjust anything in the serf layer. I think you instead want to expose these as Server configs:

nomad/nomad/config.go

Lines 127 to 139 in 7ab84c2

	// EvalGCInterval is how often we dispatch a job to GC evaluations
	EvalGCInterval time.Duration
	// EvalGCThreshold is how "old" an evaluation must be to be eligible
	// for GC. This gives users some time to debug a failed evaluation.
	EvalGCThreshold time.Duration
	// NodeGCInterval is how often we dispatch a job to GC failed nodes.
	NodeGCInterval time.Duration
	// NodeGCThreshold is how "old" a nodemust be to be eligible
	// for GC. This gives users some time to view and debug a failed nodes.
	NodeGCThreshold time.Duration

.

You can see how the Core scheduler uses these to GC nodes:

nomad/nomad/core_sched.go

Lines 131 to 132 in 7ab84c2

	cutoff := time.Now().UTC().Add(-1 * c.srv.config.NodeGCThreshold)
	oldThreshold := tt.NearestIndex(cutoff)

.

I think we can either close this PR or modify it to expose the above instead.

[gregory-m]

No problem. I will open another pull request.

[dadgar]

Thanks!

[github-actions]

I'm going to lock this pull request because it has been closed for 120 days ⏳. This helps our maintainers find and focus on the active contributions.
If you have found a problem that seems related to this change, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.