[SERVER-47420] Retry StaleVersion errors in $out and $merge code to avoid failing on secondaries Created: 08/Apr/20 Updated: 27/Apr/20 Resolved: 27/Apr/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Arun Banala | Assignee: | Arun Banala |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Operating System: | ALL | ||||
| Backport Requested: |
v4.4
|
||||
| Sprint: | Query 2020-04-20, Query 2020-05-04 | ||||
| Participants: | |||||
| Description |
|
When an aggregate $out and $merge runs on secondary of a sharded cluster, it can fail if the DBVersion on secondary is not up to date causing the error to be returned to the client |
| Comments |
| Comment by Arun Banala [ 27/Apr/20 ] |
|
Based on the discussion with sharding, the scenario of running aggreation command by directly connecting to a shard is not something we want to support. So I'm marking this ticket as won't do. |