[SERVER-61461] update_shard_key_doc_moves_shards.js fails due to spurious refreshes from secondaries Created: 12/Nov/21 Updated: 29/Oct/23 Resolved: 02/Dec/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.0.6, 4.4.11 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Luis Osta (Inactive) | Assignee: | Luis Osta (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam1 | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Backport Requested: |
v5.1, v5.0, v4.4
|
||||||||||||||||
| Sprint: | Sharding 2021-11-29, Sharding 2021-12-13 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 56 | ||||||||||||||||
| Story Points: | 1 | ||||||||||||||||
| Description |
|
Background Problem The test calls refreshCatalogCacheForNs in order to make sure that the nodes are consistently refreshed. While this refreshes the primary, it does not refresh the secondary. This means that, due to mirrored reads, we could get spurious and unexpected refreshes on the primary. There are a few possible solutions:
|
| Comments |
| Comment by Githook User [ 02/Dec/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: (cherry picked from commit c3402c98def4ce8b25609429ccb9e24fb4fe7cd0) |
| Comment by Githook User [ 02/Dec/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: (cherry picked from commit c3402c98def4ce8b25609429ccb9e24fb4fe7cd0) |
| Comment by Githook User [ 02/Dec/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: (cherry picked from commit c3402c98def4ce8b25609429ccb9e24fb4fe7cd0) |
| Comment by Githook User [ 02/Dec/21 ] |
|
Author: {'name': 'Luis Osta', 'email': 'luis.osta@mongodb.com', 'username': 'LuisOsta'}Message: |
| Comment by Max Hirschhorn [ 29/Nov/21 ] |
|
After discussing this ticket in our storypointing meeting, it seems like we could instead raise the maxTransactionLockRequestTimeoutMillis server parameter on the shards (analogous to what
which use the jstests/sharding/libs/update_shard_key_helpers.js library and have been observed to fail. (The jstests/sharding/update_compound_shard_key.js test hasn't been observed to fail.) |