[DOCS-16119] [Server] Re-enable agg_merge_when_not_matched_insert.js in config_fuzzer passthrough suites Created: 10/May/23  Updated: 13/Nov/23  Resolved: 12/Jul/23

Status: Closed
Project: Documentation
Component/s: Server
Affects Version/s: None
Fix Version/s: 7.1.0-rc0, 7.0.1, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Task Priority: Major - P3
Reporter: Backlog - Core Eng Program Management Team Assignee: Alison Huh
Resolution: Fixed Votes: 0
Labels: quick-win
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Documented
documents SERVER-73866 Re-enable agg_merge_when_not_matched_... Closed
Participants:
Days since reply: 24 weeks, 5 days ago

 Description   
Original Downstream Change Summary

This has changed the `maxCatchUpPercentageBeforeBlockingWrites` parameter to be settable both at startup (as before) and at runtime (new). We should update the server parameters doc section about this parameter. Here is the link to the doc in question: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.maxCatchUpPercentageBeforeBlockingWrites

We should replace the line:
"You cannot change
maxCatchUpPercentageBeforeBlockingWrites
during runtime."
With:
"During runtime, you can also set the parameter with the setParameter command:

db.adminCommand(

{ setParameter: 1, maxCatchUpPercentageBeforeBlockingWrites: 20}

)"

Similar to the last two sentences in this section: https://www.mongodb.com/docs/manual/reference/parameters/#mongodb-parameter-param.enableShardedIndexConsistencyCheck.
Though we should specify that this is only settable at runtime from 7.1.

Description of Linked Ticket

The test (which performs concurrent user writes an chunk migrations)is currently blacklisted from config fuzzer passthrough suites because it is sensitive to specific values of a threshold parameter (details described here).

In order to re-enable it, we can either tolerate timeout errors or exclude the execution of migration when the server parameter regulating the migration goes below a threshold value (to be qualified).



 Comments   
Comment by Allison Easton [ 18/Aug/23 ]

Hi! We ended up backporting SERVER-73866 to 7.0.1. This means that the docs should be updated for 7.1 as well as 7.0.1 (or at least we should change the update saying the parameter is settable at runtime on versions 7.0.1+ rather than 7.1+.

Generated at Thu Feb 08 08:14:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.