[SERVER-53394] Make ShardingTaskExecutorPoolReplicaSetMatching default to disabled for MongoD Created: 16/Dec/20 Updated: 29/Oct/23 Resolved: 29/Jan/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0, 4.2.13, 4.4.5 |
| Type: | Improvement | Priority: | Critical - P2 |
| Reporter: | Benjamin Caimano (Inactive) | Assignee: | George Wangensteen |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||
| Backport Requested: |
v4.4, v4.2
|
||||||||||||||||||||
| Sprint: | Service Arch 2021-02-08 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||
| Description |
|
We currently set ShardingTaskExecutorPoolReplicaSetMatching to "matchPrimaryNode" by default for both MongoD and MongoS (see here). However, the "matchPrimaryNode" behavior can be problematic for topologies when multiple shardsvrs experience a rapid influx of cross-shard operations. We should disable this behavior on MongoD nodes but not MongoS nodes. |
| Comments |
| Comment by Githook User [ 17/Feb/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: (cherry picked from commit ac99b5cf6202e2941220a1f5f56b8223af1841e9) |
| Comment by Githook User [ 08/Feb/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: (cherry picked from commit ac99b5cf6202e2941220a1f5f56b8223af1841e9) |
| Comment by Githook User [ 27/Jan/21 ] |
|
Author: {'name': 'George Wangensteen', 'email': 'george.wangensteen@mongodb.com', 'username': 'gewa24'}Message: |