[SERVER-61268] Fixing the release of a recoverable critical section on secondaries Created: 05/Nov/21 Updated: 29/Oct/23 Resolved: 08/Nov/21 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Sharding |
| Affects Version/s: | None |
| Fix Version/s: | 5.2.0, 5.1.2, 5.0.6 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Sergi Mateo Bellido |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | SSCCL-BUG, sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Backport Requested: |
v5.1, v5.0
|
||||
| Sprint: | Sharding EMEA 2021-11-15 | ||||
| Participants: | |||||
| Description |
|
Similarly to what we do for the in-memory critical sections on secondaries, when we release a recoverable critical section we should clear the filtering metadata on secondary nodes. |
| Comments |
| Comment by Githook User [ 24/Nov/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit 071c3d001d4fd11de9d8f644e15ea9bd269ceb35) |
| Comment by Githook User [ 24/Nov/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: (cherry picked from commit 071c3d001d4fd11de9d8f644e15ea9bd269ceb35) |
| Comment by Githook User [ 08/Nov/21 ] |
|
Author: {'name': 'Sergi Mateo Bellido', 'email': 'sergi.mateo-bellido@mongodb.com', 'username': 'smateo'}Message: |