Skip to:
When Operator reconfigured replica set, it does not set writeConcernMajorityJournalDefault, so it always gets the default value of true.
This is problematic and confusing if user has configured replica set to use writeConcernMajorityJournalDefault:false
writeConcernMajorityJournalDefault:false
How to repeat:
Set up Operator and create cluster with all default settings as shown in
Once the cluster has been built, log in to rs0 primary, and reconfigure replica set like:
Verify with rs.conf(), make sure it shows writeConcernMajorityJournalDefault:false
Next, scale rs0 to 5 pods from default 3, by changing and applying cr.yaml:
Apply the changes, wait for replica set to be scaled up, and check rs.conf() on rs0 primary again.
It now shows writeConcernMajorityJournalDefault: true, which was not expected.
writeConcernMajorityJournalDefault: true,
Hi,
Verified. The writeConcernMajorityJournalDefault is not changed.
writeConcernMajorityJournalDefault
The issue was fixed.
When Operator reconfigured replica set, it does not set writeConcernMajorityJournalDefault, so it always gets the default value of true.
This is problematic and confusing if user has configured replica set to use
writeConcernMajorityJournalDefault:falseHow to repeat:
Set up Operator and create cluster with all default settings as shown in
Once the cluster has been built, log in to rs0 primary, and reconfigure replica set like:
Verify with rs.conf(), make sure it shows
writeConcernMajorityJournalDefault:falseNext, scale rs0 to 5 pods from default 3, by changing and applying cr.yaml:
Apply the changes, wait for replica set to be scaled up, and check rs.conf() on rs0 primary again.
It now shows
writeConcernMajorityJournalDefault: true,which was not expected.