Matthew Oliver 1de9834816 Report final in_progress when sharding is complete ... On every sharder cycle up update in progress recon stats for each sharding container. However, we tend to not run it one final time once sharding is complete because the DB state is changed to SHARDED and therefore the in_progress stats never get their final update. For those collecting this data to monitor, this makes sharding/cleaving shards never complete. This patch, adds a new option `recon_shared_timeout` which will now allow sharded containers to be processed by `_record_sharding_progress()` after they've finished sharding for an amount of time. Change-Id: I5fa39d41f9cd3b211e45d2012fd709f4135f595e		2021-02-26 15:56:30 +00:00
..
cover-post.yaml	Add coverage reports to py27/35/36 unit test jobs	2018-10-10 23:17:00 +00:00
install_dependencies.yaml	Report final in_progress when sharding is complete	2021-02-26 15:56:30 +00:00