[SERVER-54345] Check for leftover data on shard collection is using namespace, but there is no namespace in config.chunks Created: 05/Feb/21 Updated: 29/Oct/23 Resolved: 22/Feb/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.9.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Marcos José Grillo Ramirez | Assignee: | Marcos José Grillo Ramirez |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | Sharding-EMEA, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||
| Operating System: | ALL | ||||||||||||||||
| Steps To Reproduce: | 0. Start a shard collection with namespace a.b |
||||||||||||||||
| Participants: | |||||||||||||||||
| Linked BF Score: | 12 | ||||||||||||||||
| Description |
|
After SERVER-53105 the config.chunks collection changed to refer chunks from namespace to UUID, however, the shard collection legacy path is still using namespace to check for leftover data, which will cause the path to keep going and fail later on without informing there is some manual intervention needed. This is essential for our test infrastructure on some tests to cleanup and retry the operation. |
| Comments |
| Comment by Githook User [ 22/Feb/21 ] |
|
Author: {'name': 'Marcos José Grillo Ramirez', 'email': 'marcos.grillo@mongodb.com', 'username': 'm4nti5'}Message: ... of previous failed executions using uuid and wait for majority write concern after index creation on the shard collection legacy path |