Mahmood Ali b475ccbe3e client: synchronize access to ar.alloc ... `allocRunner.alloc` is protected by `allocRunner.allocLock`, so let's use `allocRunner.Alloc()` helper function to access it.		2019-05-21 09:55:05 -04: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	docs: changelog entry for #5669 and fix comment	2019-05-14 10:54:00 -07:00
alloc_runner.go	client: do not restart dead tasks until server is contacted (try 2)	2019-05-14 10:53:27 -07: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	client: emit event and call exited hooks during cleanup	2019-03-05 15:12:02 -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