[SERVER-74600] Fix test bugs due to secondary reads in `merge_all_chunks_on_shard.js` Created: 03/Mar/23 Updated: 29/Oct/23 Resolved: 17/Mar/23 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | 7.0.0-rc0 |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Pierlauro Sciarelli | Assignee: | Pierlauro Sciarelli |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||
| Backwards Compatibility: | Fully Compatible | ||||||||||||
| Sprint: | Sharding EMEA 2023-03-20 | ||||||||||||
| Participants: | |||||||||||||
| Linked BF Score: | 141 | ||||||||||||
| Description |
|
REASON 1 The purpose of this assertion is to make sure the configurable interval to re-trigger the auto-merge is respected. The original idea was to keep it at 5 seconds to pad some slack, however on slow test variants this seems not to be enough because a CSRS secondary could be very lagged causing this query to find no documents. REASON 2 When splitting/merging chunks continuously within this loop, it can happen that the refresh triggered on the router when serving the split request goes to a secondary, not acknowledging the merge that happened right before. |
| Comments |
| Comment by Githook User [ 17/Mar/23 ] |
|
Author: {'name': 'Silvia Surroca', 'email': 'silvia.surroca@mongodb.com', 'username': 'silviasuhu'}Message: |
| Comment by Githook User [ 13/Mar/23 ] |
|
Author: {'name': 'Pierlauro Sciarelli', 'email': 'pierlauro.sciarelli@mongodb.com', 'username': 'pierlauro'}Message: |