97d32bb7d7
The health status and probe log of containers are not mission-criticial data which must survive a crash. It is not worth prematrely wearing out consumer-grade flash storage by overwriting and fsync()ing the container config on after every probe. Update only the live Container object and the ViewDB replica on every container health probe instead. It will eventually get checkpointed along with some other state (or config) change. Running containers will not be checkpointed on daemon shutdown when live-restore is enabled, but it does not matter: the health status and probe log will be zeroed out when the daemon starts back up. Signed-off-by: Cory Snider <csnider@mirantis.com> |
||
---|---|---|
.. | ||
stream | ||
archive_windows.go | ||
attach_context.go | ||
container.go | ||
container_unit_test.go | ||
container_unix.go | ||
container_windows.go | ||
env.go | ||
env_test.go | ||
exec.go | ||
health.go | ||
history.go | ||
memory_store.go | ||
memory_store_test.go | ||
monitor.go | ||
mounts_unix.go | ||
mounts_windows.go | ||
state.go | ||
state_test.go | ||
store.go | ||
view.go | ||
view_test.go |