[SERVER-71056] Recoverable critical section generically reacts to document updates to enter the commit phase Created: 03/Nov/22 Updated: 29/Oct/23 Resolved: 12/Dec/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.3.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Antonio Fuschetto | Assignee: | Antonio Fuschetto |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Sharding EMEA 2022-12-12 |
| Participants: |
| Description |
|
The recoverable critical section enters the commit phase when there is a generic update of the corresponding document in the config.collection_critical_sections collection, without considering the actual status of the blockReads field value. The observer should check that the blockReads is set before enter the commit phase of the critical section. See also this comment. |
| Comments |
| Comment by Githook User [ 12/Dec/22 ] |
|
Author: {'name': 'Antonio Fuschetto', 'email': 'antonio.fuschetto@mongodb.com', 'username': 'afuschetto'}Message: |