[SERVER-74555] Re-introduce majority commit point advancement notification mechanism and use for change streams Created: 02/Mar/23 Updated: 29/Oct/23 Resolved: 21/Apr/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0, 7.1.0-rc0 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | David Storch | Assignee: | Denis Grebennicov |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||||||||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||||||||||||||||||||||||||
| Backport Requested: |
v7.0
|
||||||||||||||||||||||||||||||||||||
| Sprint: | QE 2023-04-03, QE 2023-04-17, QE 2023-05-01 | ||||||||||||||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||||||||||||||
| Linked BF Score: | 35 | ||||||||||||||||||||||||||||||||||||
| Description |
|
An optimization to only wake up a tailable + awaitData cursor when the majority commit point advances (when reading only majority committed data) was originally introduced in The work for this ticket is to continue investigating the reason for this high CPU utilization on secondaries. Once we understand the problem better, we should reimplement |
| Comments |
| Comment by Githook User [ 24/Apr/23 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: |
| Comment by Githook User [ 21/Apr/23 ] |
|
Author: {'name': 'Denis Grebennicov', 'email': 'denis.grebennicov@mongodb.com', 'username': 'denis631'}Message: |
| Comment by Kyle Suarez [ 07/Mar/23 ] |
|
sebastien.mendez@mongodb.com, sending this to your team to discuss re-scheduling this work. CC bernard.gorman@mongodb.com, denis.grebennicov@mongodb.com |