-
Notifications
You must be signed in to change notification settings - Fork 25.6k
Introduce node mappings stats #89807
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
Changes from all commits
2ba7c33
135cb89
27d464d
2821d2c
8106602
df7184e
52ddbc1
3a13df5
421771d
2f47e2c
8bc90ec
760cfda
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,5 @@ | ||
| pr: 89807 | ||
| summary: Introduce node mappings stats | ||
| area: "Stats" | ||
| type: enhancement | ||
| issues: [] |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -226,7 +226,11 @@ GET _cat/shards?v=true | |
|
|
||
| The exact resource usage of each mapped field depends on its type, but a rule | ||
| of thumb is to allow for approximately 1kB of heap overhead per mapped field | ||
| per index held by each data node. You must also allow enough heap for {es}'s | ||
| per index held by each data node. In a running cluster, you can also consult the | ||
| <<cluster-nodes-stats,Nodes stats API>>'s `mappings` indices statistic, which | ||
| reports the number of field mappings and an estimation of their heap overhead. | ||
|
Comment on lines
+229
to
+231
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I think we should consider rephrasing this whole section in terms of these stats now that they're available. We can however do that in a followup - it's the third item on the list for #86639.
Contributor
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sure, feel free to gather ideas already here if you'd like. cc @original-brownbear
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I'm fine with a follow-up, linking from here is fine by me for now. |
||
|
|
||
| Additionally, you must also allow enough heap for {es}'s | ||
| baseline usage as well as your workload such as indexing, searches and | ||
| aggregations. 0.5GB of extra heap will suffice for many reasonable workloads, | ||
| and you may need even less if your workload is very light while heavy workloads | ||
|
|
||
Uh oh!
There was an error while loading. Please reload this page.