Sometimes it is helpful to specify one or more preferred
replica set secondaries explicitly, for example when
you for some reason cannot or don't want to tag instances,
but still have a clear preference from which servers you
want your backup to read.
This patch adds a new --replication.preferred_members
parameter that expects one or more replica set members
in the form replset-name/host:port. If a host matches
on of the names specified (separated by commas), they
get their score bumped to ensure they are the chosen
backup source.
Again: Please excuse the messy history. GitHub has broken
clean PR workflows.
Sometimes it is helpful to specify one or more preferred replica set secondaries explicitly, for example when you for some reason cannot or don't want to tag instances, but still have a clear preference from which servers you want your backup to read.
This patch adds a new --replication.preferred_members parameter that expects one or more replica set members in the form
replset-name/host:port. If a host matches on of the names specified (separated by commas), they get their score bumped to ensure they are the chosen backup source.Again: Please excuse the messy history. GitHub has broken clean PR workflows.