[SERVER-69222] random_moveChunk_multi_update_delete_change_streams.js should check for the change stream events at the end Created: 29/Aug/22 Updated: 29/Oct/23 Resolved: 22/Sep/22 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 6.2.0-rc0 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Sergi Mateo Bellido | Assignee: | Jordi Serra Torrens |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | sharding-wfbf-day | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Sprint: | Sharding EMEA 2022-10-03 | ||||
| Participants: | |||||
| Linked BF Score: | 6 | ||||
| Description |
|
Rather than having a FSM state that verifies that all performed operations are seen at the level of change streams, we should do it just once, at the very end. Note that other approaches like trying to reduce the NoopIntervalPeriodicSeconds doesn't work: this parameter can only be changed at STARTUP, so in the context of a FSM we are not able to modify it. We might need to backport this fix to 6.0. |
| Comments |
| Comment by Githook User [ 22/Sep/22 ] |
|
Author: {'name': 'Jordi Serra Torrens', 'email': 'jordi.serra-torrens@mongodb.com', 'username': 'jordist'}Message: |