Mahmood Ali 3d89ae0f1e task runner to avoid running task if terminal ... This change fixes a bug where nomad would avoid running alloc tasks if the alloc is client terminal but the server copy on the client isn't marked as running. Here, we fix the case by having task runner uses the allocRunner.shouldRun() instead of only checking the server updated alloc. Here, we preserve much of the invariants such that `tr.Run()` is always run, and don't change the overall alloc runner and task runner lifecycles. Fixes https://github.com/hashicorp/nomad/issues/5883		2019-06-27 11:27:34 +08:00
..
interfaces	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
state	stale allocation data leads to incorrect (and even negative) metrics (#5637)	2019-05-07 15:54:36 -04:00
taskrunner	task runner to avoid running task if terminal	2019-06-27 11:27:34 +08:00
alloc_runner.go	client/allocrunner: depend on internal task state	2019-06-10 18:42:51 -04:00
alloc_runner_hooks.go	client: synchronize access to ar.alloc	2019-05-21 09:55:05 -04:00
alloc_runner_test.go	Update deployment health on failed allocations only if health is unset	2019-05-02 22:59:56 -05:00
alloc_runner_unix_test.go	task runner to avoid running task if terminal	2019-06-27 11:27:34 +08:00
allocdir_hook.go	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
config.go	client: do not restart dead tasks until server is contacted (try 2)	2019-05-14 10:53:27 -07:00
health_hook.go	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
health_hook_test.go	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
migrate_hook.go	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
testing.go	client: do not restart dead tasks until server is contacted (try 2)	2019-05-14 10:53:27 -07:00
upstream_allocs_hook.go	client: cleanup and document context uses	2019-03-12 15:03:54 -07:00
util.go	allocrunnerv2 -> allocrunner	2018-10-16 16:56:56 -07:00