tree 1a84f053b30be4bf66d50cbe680b4319aef0fe1f
parent 0e51c2702a20a1c9318446a35db01514563abbf0
author Kashif Faraz <kashif.faraz@gmail.com> 1685416893 +0530
committer GitHub <noreply@github.com> 1685416893 +0530
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJkdWu9CRBK7hj4Ov3rIwAADqsIACN3Mw0BHDfeYTGbke+9VtZ7
 Xjfo4L/HGvzjeHrwGe2QnG+mmajr93PA2OgN+GPkD/N7a3gS9b92b1jFZ9STqnUR
 BTa7VALVkichniOZ4W3wgaAGtccCvHMNo2fRz8C54uwpDXkyAQ1FH3Ye0xDvMaTS
 50d9A2CvwDSmEOzqf0B5aNTBlLWP321SbnEuU4wxYe+0x0eybWIHPUQnbK5VbDCM
 RMGuVo5RAJ7F1emd2S1qCG1I3Du2W9kL/u/kuH9SBMGLH0tcRIw4a6O9kF3XFRUc
 iRPxMbpW+h9x0jJ4auEM29L7xo2F7k/ZKl/gNC8foCUkOdW1hbX6v6K9O9GjHYs=
 =nawK
 -----END PGP SIGNATURE-----
 

Update default values in CoordinatorDynamicConfig (#14269)

The defaults of the following config values in the `CoordinatorDynamicConfig` are being updated.

1. `maxSegmentsInNodeLoadingQueue = 500` (previous = 100)
2. `replicationThrottleLimit = 500` (previous = 10)
Rationale: With round-robin segment assignment now being the default assignment technique,
the Coordinator can assign a large number of under-replicated/unavailable segments very quickly,
without getting stuck in `RunRules` duty due to very slow strategy-based cost computations.

3. `maxSegmentsToMove = 100` (previous = 5)
Rationale: A very low value (say 5) is ineffective in balancing especially if there are many segments
to balance. A very large value can cause excessive moves, which has these disadvantages:
- Load of moving segments competing with load of unavailable/under-replicated segments
- Unnecessary network costs due to constant download and delete of segments

These defaults will be revisited after #13197 is merged.