Consider eliminating chronicle push wherever possible by doing quorum read in the remotely called functions

Quorum reads will need to be done before janitor:cleanup, failover, rebalance

Aliaksey: But janitor_agent doesn't ever read the vbucket map.
Artem: and any other keys?
Aliaksey:
Only flushseq from the bucket config. ns_janitor doesn't touch it, and even if it did, I think it's ok to be eventually consistent there.
6:11
Those syncs in ns_janitor are pretty new. I added them for durable writes. And the only reason I added them was to increase the probability that if leader changes, it'll find the latest config.