[SERVER-43188] Add warnings about enableMajorityReadConcern and usage of arbiters on reconfig Created: 05/Sep/19 Updated: 06/Dec/22 Resolved: 18/May/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Xuerui Fa | Assignee: | Backlog - Replication Team |
| Resolution: | Won't Fix | Votes: | 1 |
| Labels: | former-quick-wins, neweng | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Replication
|
||||||||
| Participants: | |||||||||
| Description |
|
When starting up a Primary-Secondary-Arbiter configuration architecture, the warning messages regarding majority read concern enabled (implemented in If a node in a PSA architecture goes down and restarts, it will log the warning correctly. This should also apply to nodes on a clean startup, as well as on reconfiguration. |
| Comments |
| Comment by Jericho Rivera [ 24/Jul/20 ] |
|
Seems to affect 4.0.19 and 4.2.8 releases as well. |
| Comment by Siyuan Zhou [ 09/Sep/19 ] |
|
Returning a warning in the reconfig response is another way to communicate it. Not sure if returning a warning is a good practice when also returning { ok: 1 }. |