Make requests_per_second configurable to throttle reindexing #120207
Merged
Add this suggestion to a batch that can be applied as a single commit. This suggestion is invalid because no changes were made to the code. Suggestions cannot be applied while the pull request is closed. Suggestions cannot be applied while viewing a subset of changes. Only one suggestion per line can be applied in a batch. Add this suggestion to a batch that can be applied as a single commit. Applying suggestions on deleted lines is not supported. You must change the existing code in this line in order to create a valid suggestion. Outdated suggestions cannot be applied. This suggestion has been applied or marked resolved. Suggestions cannot be applied from pending reviews. Suggestions cannot be applied on multi-line comments. Suggestions cannot be applied while the pull request is queued to merge. Suggestion cannot be applied right now. Please check back later.
This pull request primarily focuses on introducing a new setting for reindexing data streams and adding corresponding tests. The changes include adding a new setting for the maximum number of reindex requests per second, modifying the reindex method to incorporate this setting, and creating a new test class to verify the functionality.
Key changes include:
New Setting Addition:
REINDEX_MAX_REQUESTS_PER_SECOND_SETTING
to control the maximum number of reindex requests per second inReindexDataStreamIndexTransportAction
.Code Modifications:
reindex
method inReindexDataStreamIndexTransportAction
to use the newREINDEX_MAX_REQUESTS_PER_SECOND_SETTING
for reindex requests.MigratePlugin
and added it to the list of plugin settings. [1] [2]Test Enhancements:
generateDestIndexName
fromReindexDatastreamIndexTransportActionIT
and added them to a new test classReindexDataStreamIndexTransportActionTests
. [1] [2] as they are unit tests not ITs.ReindexDataStreamIndexTransportActionTests
to verify that the reindex method's reindex requests includes the rate limit setting.