[SERVER-30499] Only update sessions with a transaction number Created: 03/Aug/17 Updated: 30/Oct/23 Resolved: 03/Aug/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 3.5.12 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Jack Mulrow |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Operating System: | ALL |
| Sprint: | Sharding 2017-08-21 |
| Participants: |
| Description |
|
There are a few places in op_observer_impl.cpp and oplog.cpp that call {set,get}LastWriteOptimeTs or saveTxnProgress if a session exists on the operation context, but they should instead check the operation context has a transaction number, because the session's state isn't loaded without one.
|
| Comments |
| Comment by Githook User [ 10/Aug/17 ] |
|
Author: {'name': 'Jack Mulrow', 'email': 'jack.mulrow@mongodb.com'}Message: |