[SERVER-67402] Linearizable reads can occasionally read with wrong read source Created: 21/Jun/22 Updated: 29/Oct/23 Resolved: 08/Aug/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | 5.0.9, 6.0.0-rc10, 6.1.0-rc0 |
| Fix Version/s: | 5.0.13, 6.0.2, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Matthew Russotto | 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 | ||||||||||||||||||||
| Backport Requested: |
v6.0, v5.0
|
||||||||||||||||||||
| Sprint: | Execution Team 2022-08-08, Execution Team 2022-08-22 | ||||||||||||||||||||
| Participants: | |||||||||||||||||||||
| Description |
|
Linearizable reads are supposed to happen only on a writable primary with a read source of kNoTimestamp. Because of a race, these reads may enter AutoGetCollectionForRead on a secondary or primary in catch-up mode. Before Instead of either reading at kNoTimestamp on a secondary, or hitting an fassert, a linearizable read should uassert with NotWritablePrimary when it would otherwise open a snapshot on a non-writable node. |
| Comments |
| Comment by Githook User [ 15/Sep/22 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: (cherry picked from commit f62d857f440e1340c7338d81c128d0682305f777) |
| Comment by Githook User [ 08/Sep/22 ] |
|
Author: {'name': 'Henrik Edin', 'email': 'henrik.edin@mongodb.com', 'username': 'henrikedin'}Message: (cherry picked from commit f62d857f440e1340c7338d81c128d0682305f777) |