+user
I explicitly didn't mention "update without restart" as a criterion because
you could use a watched configuration file to achieve this, like we did for
the whitelist. If the master or agent observe any changes to the
configuration file then they can apply them. If they cannot apply the
The motivation for "dynamic" quota/weights was that we wanted operators to
be able to change these without restarting (all) masters. That means you'd
update these values via operator endpoints, and if you're doing that, then
the flag values become outdated/irrelevant, and we must persist these
Makes sense: arguably you could say that "quota" and "weights" are
part of the master's (mutable) "state", not its "configuration", which
is largely immutable.
Another distinction is that some configuration flags control behavior
that doesn't need to be consistent between master replicas (e.g.,
