Change 25796
mkrep.sh will no longer allow a standby replica to initially be
'mandtory' on startup, as required by p4d 2019.1.
If it was intended to be mandatory (i.e. has an 'ha' in the
ServerID), a new warning message id displayed describing why
that converting it to be mandatory should be considered after
it is caught up, and why.
#review @michael_shields
'mandtory' on startup, as required by p4d 2019.1.
If it was intended to be mandatory (i.e. has an 'ha' in the
ServerID), a new warning message id displayed describing why
that converting it to be mandatory should be considered after
it is caught up, and why.
#review @michael_shields
0 comments
Log in to comment
Tip: Use n and p to cycle through the changes.
|
|
Description:" > "$ServerSpecFile" || bail "Failed to initialize server spec file [$ServerSpecFile]." + +warnmsg "Server $ServerSpec is intended to have the Options: field value set to 'mandatory'. However, it is initially configured as 'nomandatory' to prevent undue stalling of a global topology while a fresh new standby replica gets caught up. As of 2019 + +After this replica is brought online, consider making it a 'mandatory' replica.
Robert Cowham (on mkrep.sh, line 493) commented
6 years ago
"After this replica is brought online and is seen to be replicating properly (and up-to-date), consider making it a 'mandatory' replica. |
| ·0 | |
|
|
|
|
|
+After this replica is brought online, consider making it a 'mandatory' replica. + +A 'mandatory' replica is one that you can trust is at least as current as all other replicas, and this is the optimal candidate for a smooth failover from the master server. However, if the 'mandatory' replica fails, it cannot be easily ignored -- it sta + +Should that ever occur, you can modify the server spec manually on the master serer, changing the 'mandatory' value to 'nomandatory'. That will enable global replication to move on. It should then be a high priority to figure out what went wrong with the |
| ·0 | |
|
|