Limit verbose log line on scheduled migration cancellation #1738
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.
Description
Small change to only limit the
Cancelling the migration process.
log line if a scheduled migration exists.This log line can be seen whenever an index is created regardless if scheduledMigration is null or non-null.
I ran into this log line when doing performance testing with the security plugin in scenarios where clusters contain a lot of indices and wrote a script to quickly create indices. This log line is pervasive when index creation is occurring.
Related Issues
Related to: #1183
Check List
--signoff
.By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.