[SERVER-31233] Session should invalidate _lastWrittenSessionRecord when it detects inconsistency during updateSessionEntry Created: 22/Sep/17 Updated: 30/Oct/23 Resolved: 26/Sep/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | 3.5.13 |
| Fix Version/s: | 3.6.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Randolph Tan | Assignee: | Randolph Tan |
| 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 | ||||
| Participants: | |||||
| Linked BF Score: | 0 | ||||
| Comments |
| Comment by Githook User [ 26/Sep/17 ] |
|
Author: {'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}Message: instead of calling onWriteOpCompletedOnPrimary directly, as there is race where the migration thread might try to retrieve the oplog with the dummy timestamp. |
| Comment by Githook User [ 25/Sep/17 ] |
|
Author: {'email': 'kaloian.manassiev@mongodb.com', 'name': 'Kaloian Manassiev', 'username': 'kaloianm'}Message: The session transaction cache must move in lock step with the disk writes This change also reverts commit 74c1946fb05b9fe955f84edd1cc441394bbe6ccf. |
| Comment by Kaloian Manassiev [ 22/Sep/17 ] |
|
There should never be inconsistency during updateSessionEntry, because all modifications go through the cache and it is the cache that is moving it forward. Is it possible that these tests are making incorrect assumptions? |
| Comment by Githook User [ 22/Sep/17 ] |
|
Author: {'email': 'randolph@10gen.com', 'name': 'Randolph Tan', 'username': 'renctan'}Message: |