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.

Sign up for GitHub

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

Jump to bottom

(Health API) Shard sizes above 50GB #115452

Closed
stefnestor opened this issue Oct 23, 2024 · 3 comments
Closed

(Health API) Shard sizes above 50GB #115452

stefnestor opened this issue Oct 23, 2024 · 3 comments
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.

Comments

@stefnestor
Copy link
Contributor

stefnestor commented Oct 23, 2024 •
edited
Loading

Description

👋 Elasticsearch recommends aiming for shards 10-50GB. Kindly consider adding a Health API for shards (egregiously) falling above recommendation.

For example, not flag redacted-01, maybe-but-probably-not flag redacted-02, but please flag redacted-03:

# GET _cat/shards?v
index        shard prirep state       docs   store ip             node
redacted-01  0     r      STARTED 64990325  34.2gb 10.172.166.107 instance-0000000011
redacted-02  1     p      STARTED 62935614  53.2gb 10.174.10.53   instance-0000000012
- redacted-03  1     p      STARTED 96426187 117.7gb 10.174.10.53   instance-0000000012

Resolution was added into above linked doc via #111254 so needed resolution content exists, we would just need Elastic to flag notice to users. 🙏
@stefnestor stefnestor added >enhancement needs:triage Requires assignment of a team area label Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. labels Oct 23, 2024
@astefan astefan added :Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) and removed needs:triage Requires assignment of a team area label labels Oct 25, 2024
@elasticsearchmachine
Copy link
Collaborator

Pinging @elastic/es-distributed (Team:Distributed)

@elasticsearchmachine elasticsearchmachine added the Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination. label Oct 25, 2024
@DaveCTurner
Copy link
Contributor

I don't think we should consider a 100+GiB shard as a health problem, i.e. one that should trigger an alert requiring some level of urgent attention from the user. It's more of an advisory point related to fine-tuning the user's cluster, and the health API is not set up for identifying that sort of thing today.

@DaveCTurner DaveCTurner closed this as not planned Won't fix, can't repro, duplicate, stale Oct 26, 2024
@stefnestor
Copy link
Contributor Author

Thanks for the response, @DaveCTurner ! ACK. Just cross-posting for future discussions: Stack Monitoring does alert this ballpark : elastic/kibana#190663 .

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
:Distributed Coordination/Allocation All issues relating to the decision making around placing a shard (both master logic & on the nodes) >enhancement Supportability Improve our (devs, SREs, support eng, users) ability to troubleshoot/self-service product better. Team:Distributed (Obsolete) Meta label for distributed team (obsolete). Replaced by Distributed Indexing/Coordination.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@astefan @DaveCTurner @stefnestor @elasticsearchmachine