[SERVER-31528] setFeatureCompatibilityVersion should accept a write concern Created: 12/Oct/17 Updated: 18/Oct/17 Resolved: 18/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Spencer Brody (Inactive) |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: |
| Description |
|
The setFeatureCompatibilityVersion command waits for writes to occur on a majority of nodes, but not all. It would be useful to be able to set the write concern higher so that users can rely on it not to return until they can safely change their binaries. This should be as easy as setting the supportsWriteConcern boolean to true. This would simply be an extra wait on the system last OpTime after the command succeeded, and would have no affect on the w: majority writes done as part of the command. |
| Comments |
| Comment by Spencer Brody (Inactive) [ 18/Oct/17 ] |
|
We already document that users need to ensure that their FCV is properly propagated on all nodes (and check by polling getParameter: featureCompatibilityVersion) before beginning another upgrade or downgrade. |