[SERVER-46646] Disallow hedging for commands that can potentially do writes Created: 05/Mar/20 Updated: 29/Oct/23 Resolved: 10/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Internal Code |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Cheahuychou Mao | Assignee: | Cheahuychou Mao |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | Sharding 2020-03-09, Sharding 2020-03-23 | ||||
| Participants: | |||||
| Description |
|
aggregate and mapReduce commands can have an "out" stage that does writes. Hedging these commands could lead to unexpected behaviors since all writes need to be routed to the primary (i.e. writes will be executed more than once). As such, we need to disallow hedging for aggregate, mapReduce and all other commands can potentially do writes. |
| Comments |
| Comment by Githook User [ 18/Mar/20 ] |
|
Author: {'email': 'cheahuychou.mao@mongodb.com', 'name': 'Cheahuychou Mao', 'username': 'cheahuychou'}Message: (cherry picked from commit dc895c373b8e48113ce7505595b05011dd02f6e4) |
| Comment by Githook User [ 10/Mar/20 ] |
|
Author: {'name': 'Cheahuychou Mao', 'username': 'cheahuychou', 'email': 'cheahuychou.mao@mongodb.com'}Message: |