Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[1.x] An allocation constraint mechanism, that de-prioritizes nodes from getting picked for allocation if they breach certain constraints #777

Merged
merged 4 commits into from
Jun 4, 2021

Conversation

ashwinpankaj
Copy link
Contributor

@ashwinpankaj ashwinpankaj commented May 26, 2021

Backport of #680 for Issue #487

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.

Ashwin Pankaj and others added 4 commits May 26, 2021 16:36
…tting picked for allocation if they breach certain constraints

Signed-off-by: Ashwin Pankaj <appankaj@amazon.com>
Signed-off-by: Ashwin Pankaj <appankaj@amazon.com>
Signed-off-by: Ashwin Pankaj <appankaj@amazon.com>
Signed-off-by: Ashwin Pankaj <appankaj@amazon.com>
@ashwinpankaj ashwinpankaj marked this pull request as ready for review May 26, 2021 11:17
@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Wrapper Validation success a3135a8

@opensearch-ci-bot
Copy link
Collaborator

✅   DCO Check Passed a3135a8

@opensearch-ci-bot
Copy link
Collaborator

✅   Gradle Precommit success a3135a8

@ashwinpankaj
Copy link
Contributor Author

Folks, since the original PR #680 has already been reviewed and merged, could you please merge this PR?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants