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

[Bug] Fix cluster health API response #9020

Open
amkhar opened this issue Aug 1, 2023 · 0 comments
Open

[Bug] Fix cluster health API response #9020

amkhar opened this issue Aug 1, 2023 · 0 comments
Labels
bug Something isn't working Cluster Manager

Comments

@amkhar
Copy link
Contributor

amkhar commented Aug 1, 2023

Describe the bug
Original Issue opened : #5098 . This issue is a sub task for the overall project defined #8098.

Description
Today, during node drop and joins, we fetch the metadata of unassigned shards on per shard basis. As part of the project #8098 we're changing the fetches to happen for a batch of shards. These async fetches are given in the response of _cluster/health API. We need to make changes to correctly reflect that value after fetch is happening at a batch level.

public int getNumberOfInFlightFetches() {
int count = 0;
for (AsyncShardFetch<TransportNodesListGatewayStartedShards.NodeGatewayStartedShards> fetch : asyncFetchStarted.values()) {
count += fetch.getNumberOfInFlightFetches();
}
for (AsyncShardFetch<TransportNodesListShardStoreMetadata.NodeStoreFilesMetadata> fetch : asyncFetchStore.values()) {
count += fetch.getNumberOfInFlightFetches();
}
return count;
}

Additional context
Please go through the discussion #5098 to understand the overall enhancement approach and check #8098 to see the sub tasks of overall project.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working Cluster Manager
Projects
Status: 🆕 New
Development

Successfully merging a pull request may close this issue.

2 participants