[SERVER-50054] Advance logicalClock on transactionParticipant to commitTimestamp upon receiving commitTransaction Created: 31/Jul/20 Updated: 29/Oct/23 Resolved: 26/Aug/20 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 4.7.0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Misha Tyulenev | Assignee: | Tommaso Tocci |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | PM-1645-Milestone-3, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding 2020-09-07 | ||||
| Participants: | |||||
| Linked BF Score: | 11 | ||||
| Description |
|
TransactionParticipant relies on the clusterTime gossiping protocol to advance its logical clock. However there are cases when cluster time gossiping is not enabled - e.g. when a receiving node is not in a readable state. |
| Comments |
| Comment by Githook User [ 26/Aug/20 ] |
|
Author: {'name': 'Tommaso Tocci', 'email': 'tommaso.tocci@mongodb.com', 'username': 'toto-dev'}Message: |
| Comment by Kevin Pulo [ 05/Aug/20 ] |
|
Yes, this ticket is the result of that same failure! |
| Comment by Kaloian Manassiev [ 04/Aug/20 ] |
|
kevin.pulo, is this possibly related to something that you and Matthew Russotto were recently investigating? |