[SERVER-62152] Investigate hang in unit tests when ShardRegistry reload on fixed executor Created: 17/Dec/21 Updated: 06/Dec/22 Resolved: 03/Feb/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | [DO NOT USE] Backlog - Sharding EMEA |
| Resolution: | Won't Fix | Votes: | 0 |
| Labels: | shardingemea-qw | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Assigned Teams: |
Sharding EMEA
|
||||||||
| Operating System: | ALL | ||||||||
| Participants: | |||||||||
| Description |
|
The AsyncTry for reloading the ShardRegistry is causing hangs in some unit tests. As a temporary solution, it was needed to commit a special case only for unit tests performing a synchronous reload. For example, by just keeping the async reload, MigrationDestinationManagerGetIndexesAndCollectionsNoVersionsOrReadConcern is hanging after logging this line:
Attaching backtrace of the hang. The thread is stuck waiting on this condition variable |
| Comments |
| Comment by Githook User [ 15/Feb/22 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |