[SERVER-76839] Operations with a CollectionCatalog instance can observe uncommitted collections become committed from a different operation operating on a different CollectionCatalog instance Created: 04/May/23 Updated: 29/Oct/23 Resolved: 08/Jun/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Gregory Wlodarek | Assignee: | Henrik Edin |
| 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: | Execution Team 2023-05-29, Execution Team 2023-06-12 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Linked BF Score: | 156 | ||||||||||||||||||||
| Description |
|
This can be reproduced with
In GDB I observed that after the wuow.commit(), _cachedCommitted stays false, but _shared->_committed flips to true in the shared state of the collection. I don't think _shared->_committed should be shared. In the example above we're thinking about crossing database boundaries through end(). But we can also have something like test.a -> test.b (uncommitted) -> test.c |
| Comments |
| Comment by Githook User [ 08/Jun/23 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: This fixes inconsistent visibility where readers all of a sudden discovered collections to be visible even though they had a stashed snapshot of the catalog. It also allows for a lot of simplifications not having to deal with "waiting for visibility" and collections are now fully visible when onCommit handlers execute. |
| Comment by Githook User [ 07/Jun/23 ] |
|
Author: {'name': 'Sviatlana Zuiko', 'email': 'sviatlana.zuiko@mongodb.com', 'username': 'szuiko'}Message: Revert " This reverts commit c212bd9f6cf4652408b395a530112e76280eb858. |
| Comment by Githook User [ 06/Jun/23 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: This fixes inconsistent visibility where readers all of a sudden discovered collections to be visible even though they had a stashed snapshot of the catalog. It also allows for a lot of simplifications not having to deal with "waiting for visibility" and collections are now fully visible when onCommit handlers execute. |