[SERVER-31589] A primary's SyncSourceFeedback only renews an OperationContext on role changes. Created: 16/Oct/17 Updated: 30/Oct/23 Resolved: 24/Oct/17 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Replication |
| Affects Version/s: | None |
| Fix Version/s: | 3.2.18, 3.4.11, 3.6.0-rc2 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Daniel Gottlieb (Inactive) | Assignee: | Pavithra Vetriselvan |
| 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 Completed: | |||||||||||||
| Sprint: | Repl 2017-10-23, Repl 2017-11-13 | ||||||||||||
| Participants: | |||||||||||||
| Description |
|
My understanding of the code may be wrong here. The SyncSourceFeedback thread refreshes its OperationContext for each iteration of the outer loop. However, there is an inner while loop that, for primaries, only breaks out when its "position" has changed or if it is no longer a primary. This can cause the OperationContext to not release underlying cursors for indefinitely long periods of time and prevent WT from dropping underlying tables. |
| Comments |
| Comment by Githook User [ 17/Nov/17 ] |
|
Author: {'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}Message: (cherry picked from commit 608f38a4fb0de96546dd0aa3eea2f244bbcf2bef) |
| Comment by Githook User [ 17/Nov/17 ] |
|
Author: {'name': 'Pavithra Vetriselvan', 'email': 'pavithra.vetriselvan@mongodb.com'}Message: (cherry picked from commit 608f38a4fb0de96546dd0aa3eea2f244bbcf2bef) |
| Comment by Githook User [ 24/Oct/17 ] |
|
Author: {'email': 'pavithra.vetriselvan@mongodb.com', 'name': 'Pavithra Vetriselvan'}Message: |
| Comment by Daniel Gottlieb (Inactive) [ 16/Oct/17 ] |
|
spencer Similar to |