Improve logging message for no shards found to indicate that export m… #3681
+21
−7
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.
…ay still be ongoing
Description
Reduces the logging for no shards acquired to every 50 retries (approximately every 12 minutes) and only if there are no shards being processed at the time on the node, with an error message that indicates this may be due to either all shards being consumed already (by other nodes), or that an export is still in progress if export is configured.
This log makes it so that when no shards are available or the export is ongoing, we will not just see this as the final log
Which makes the node appear stuck and like it is not doing anything
Check List
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.