You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 18, 2018. It is now read-only.
We currently optimise placement generation/modification logic to maximise randomness when distributing shards, so as to evenly distribute load. This gets in the way of our ability to rollout new versions to a single replica.
Put another way, we run M3DB with replication factor 3. To minimise risk during rollout, we'd like the ability to rollout to a single node in each "replica set". We should enhance our placement algorithm to support this.
The text was updated successfully, but these errors were encountered:
Sounds like what you want is the mirrored placement, which the new agg tier also needs. @cw9 has made good progress on that front so I'll let him chime in here.
Yeah it's kinda like that, dunno what approach you've taken for it. I was thinking we can accomplish this without any interface changes to the placement, only implementation of the placement algorithm.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We currently optimise placement generation/modification logic to maximise randomness when distributing shards, so as to evenly distribute load. This gets in the way of our ability to rollout new versions to a single replica.
Put another way, we run M3DB with replication factor 3. To minimise risk during rollout, we'd like the ability to rollout to a single node in each "replica set". We should enhance our placement algorithm to support this.
The text was updated successfully, but these errors were encountered: