[SERVER-72525] Randomly choose between FCBIS and logical initial sync every time in our testing Created: 04/Jan/23 Updated: 13/Jul/23 |
|
| Status: | Open |
| Project: | Core Server |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Engineering Test | Priority: | Major - P3 |
| Reporter: | Judah Schvimer | Assignee: | Backlog - Replication Team |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | former-quick-wins | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||
| Assigned Teams: |
Replication
|
||||||||||||||||
| Sprint: | Repl 2023-04-17 | ||||||||||||||||
| Participants: | |||||||||||||||||
| Description |
|
Today there is a lot of testing for logical initial sync that isn't matched by FCBIS tests. Every time we spin up an enterprise node in our tests we should randomly choose between initial sync methods. Sometimes FCBIS may not be possible, but in those cases it will fall back on logical initial sync. We should ensure that fallback doesn't significantly increase the test duration. |
| Comments |
| Comment by Louis Williams [ 09/Jan/23 ] |
|
Could we use the config fuzzer for this? It's easily expandable to add new parameters and avoids having to make specific suites to fuzz this parameter. We'll just need to make sure we have a config_fuzzer suite that performs initial sync. |