[SERVER-66566] Optimize scanning SessionCatalog when refreshing retryable writes from storage Created: 18/May/22 Updated: 29/Oct/23 Resolved: 19/May/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.0.0-rc7, 6.1.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Jack Mulrow | Assignee: | Cheahuychou Mao |
| 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
|
||||
| Sprint: | Sharding NYC 2022-05-30 | ||||
| Participants: | |||||
| Description |
|
To support retryable writes that execute statements as transactions, when refreshing a retryable write from storage, we scan the session catalog for the highest txnNumber for that session. Scanning the catalog locks it, so we should optimize this scan to leverage the changes from |
| Comments |
| Comment by Githook User [ 19/May/22 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: (cherry picked from commit c08864097934c74da40ffff9ea46176fb471ead5) |
| Comment by Githook User [ 19/May/22 ] |
|
Author: {'name': 'Cheahuychou Mao', 'email': 'mao.cheahuychou@gmail.com', 'username': 'cheahuychou'}Message: |