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

[Backport 1.1] [BUG] fix healthcheck logic to expect object and return ids #2303

Merged
merged 1 commit into from
Sep 12, 2022

Conversation

opensearch-trigger-bot[bot]
Copy link
Contributor

Backport e10ba34 from #2300

…2300)

Original implementation incorrectly assumed the return list of
nodes was an object array.
This PR:
#2232

Addressed the return but didn't catch the nodes.find in the return
which is a function for an array.

Also, refactors to return a list of node_ids because the original
implementation indicated that it should but it can return node ids
but it never did. It only returned `null` or `_local`, the problem
with this approach is that it doesn't expect valid node version
with different DIs or filter out nodes when we pass `null` as the node
ID for the node info call because it was fan out the request to all
nodes.

Now this function will return `_local` if all the nodes share the
same cluster_id using a greedy approach since we can assume it is
all the same version.

Will return node ids, if the cluster_id are different so it will
pass a CSV to the node info call and return the info for those nodes.
And null if no cluster_id is present, ie, fan out the response.

Original issue:
#2203

Signed-off-by: Kawika Avilla <[email protected]>

Signed-off-by: Kawika Avilla <[email protected]>
(cherry picked from commit e10ba34)
@kavilla kavilla changed the title [Backport 1.1] [Backport 1.x] [BUG] fix healthcheck logic to expect object and return ids [Backport 1.1] [BUG] fix healthcheck logic to expect object and return ids Sep 8, 2022
@Flyingliuhub Flyingliuhub merged commit 3877f98 into 1.1 Sep 12, 2022
@kavilla kavilla deleted the backport/backport-2300-to-1.1 branch November 23, 2022 09:09
@joshuarrrr joshuarrrr added the not in release PRs backported to already shipped releases with no future release planned label Mar 10, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
not in release PRs backported to already shipped releases with no future release planned
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants