[SERVER-31388] multiVersion/mixed_storage_version_replication.js may enter infinite loop of listCollections Created: 04/Oct/17 Updated: 30/Oct/23 Resolved: 05/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jonathan Reams | Assignee: | Jonathan Reams |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Platforms 2017-10-23 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Description |
|
In mixed_storage_version_replication.js, there are a bunch of threads that are dropping, creating, inserting, deleting, indexing, etc. To decide which collection to operate on, the test would listDatabases. If that database only had one collection, it would return null, otherwise while a random collection from the database was "system.indexes" it would re-list collections from that database. Every so often, it would hit a database that had two collections, and then while it was looking for a collection that wasn't "system.indexes", a collection would be dropped and then it would be in an infinite loop of looking for a new collection. This causes the test to hang. |
| Comments |
| Comment by Githook User [ 05/Oct/17 ] |
|
Author: {'email': 'jbreams@mongodb.com', 'name': 'Jonathan Reams', 'username': 'jbreams'}Message: |