[SERVER-51070] Get rid of writeConfigServerDirect for writes to the ConfigServer database Created: 21/Sep/20 Updated: 29/Oct/23 Resolved: 04/Dec/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Eric Maynard | Assignee: | Kaloian Manassiev |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Sprint: | Sharding 2020-11-30, Sharding 2020-12-14 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 17 | ||||||||||||||||
| Description |
|
Note that policy is labelled not idempotent, but it seems like there is a case when the write can be applied more than once in the server as seen on the linked BF. Investigate whether isNotPrimaryError it is actually safe to retry with this error. |
| Comments |
| Comment by Githook User [ 04/Dec/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: Due to a legacy check on the Config Server, commands sent there cannot |
| Comment by Githook User [ 03/Dec/20 ] |
|
Author: {'name': 'Kaloian Manassiev', 'email': 'kaloian.manassiev@mongodb.com', 'username': 'kaloianm'}Message: ... so components lower on the stack don't need to link ShardRegistry. |