[SERVER-65407] In ShardingCatalogManager::commitChunkMigration() operations on config DB should pass config arg Created: 09/Apr/22 Updated: 29/Oct/23 Resolved: 29/Apr/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Andrew Shuvalov (Inactive) | Assignee: | Andrew Shuvalov (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-nyc-subteam2, sharding-nyc-subteam2-catalog-poc | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||
| Operating System: | ALL | ||||||||
| Steps To Reproduce: | It's related to |
||||||||
| Sprint: | Sharding NYC 2022-04-18, Sharding 2022-05-02 | ||||||||
| Participants: | |||||||||
| Story Points: | 1 | ||||||||
| Description |
|
When calling runCommandWithFixedRetryAttempts() the database name should be `NamespaceString::kAdminDb.toString()` and not `nss.db().toString()`. It matters for our catalog shard related code because we need to assert that catalog shard and co-located regular shard are not invoked improperly. As the code is more strict it fails on this liberty. |
| Comments |
| Comment by Githook User [ 22/Apr/22 ] |
|
Author: {'name': 'Kshitij Gupta', 'email': 'kshitij.gupta@mongodb.com', 'username': 'kshitijng'}Message: |
| Comment by Githook User [ 11/Apr/22 ] |
|
Author: {'name': 'Andrew Shuvalov', 'email': 'andrew.shuvalov@mongodb.com', 'username': 'shuvalov-mdb'}Message: |