[SERVER-31877] removeShard logic should use majority writeConcern (instead of local) for writes Created: 08/Nov/17 Updated: 27/Oct/23 Resolved: 21/Nov/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.6.0-rc3 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Esha Maharishi (Inactive) | Assignee: | Esha Maharishi (Inactive) |
| Resolution: | Works as Designed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Operating System: | ALL |
| Sprint: | Sharding 2017-11-13, Sharding 2017-12-04 |
| Participants: |
| Comments |
| Comment by Esha Maharishi (Inactive) [ 21/Nov/17 ] |
|
Mongos passes majority writeConcern for the removeShard command, so the individual writes should not need to be done with majority. |
| Comment by Esha Maharishi (Inactive) [ 08/Nov/17 ] |
|
renctan yes, this seems like a regression from 3.4... When removeShard was moved from mongos to the config server in |
| Comment by Randolph Tan [ 08/Nov/17 ] |
|
I thought we made mongos send w: majority for all config commands? |