Improve Health Status of lock Index in Single Node Clusters #807
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
Bug Fix: Improve Health Status of .opendistro-job-scheduler-lock Index in Single Node Clusters
This pull request addresses an issue where the
.opendistro-job-scheduler-lock
index was showing a yellow health status in single node clusters. The problem was caused by the use ofindexrequest
default settings, which were not optimal for single node environments.Changes:
.opendistro-job-scheduler-lock
index to:Issues Resolved
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.