[SERVER-46440] Routing info should be reloaded before retry of creating session collection index on stale config error Created: 26/Feb/20 Updated: 29/Oct/23 Resolved: 12/Mar/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.4.0-rc0, 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Alexander Taskov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-4.4-stabilization | ||
| 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-23 | ||||
| Participants: | |||||
| Description |
|
When creating the sessions collection index, the config server will retry on stale config errors because as of 4.4 createIndexes uses the shard version protocol. Sending the command uses a routing info gotten outside the retry loop, so the same stale routing info will be used by each retry. Instead the routing info should be reloaded between retries. |
| Comments |
| Comment by Githook User [ 24/Mar/20 ] |
|
Author: {'name': 'Alex Taskov', 'username': 'alextaskov', 'email': 'alex.taskov@mongodb.com'}Message: (cherry picked from commit 4e329f262b5c083068700930177d2eb003241273) |
| Comment by Githook User [ 12/Mar/20 ] |
|
Author: {'username': 'alextaskov', 'name': 'Alex Taskov', 'email': 'alex.taskov@mongodb.com'}Message: |
| Comment by Jack Mulrow [ 26/Feb/20 ] |
|
The query team added a shardVersionRetry helper template that might be useful here. |