ECK - Increase default Kibana memory limit to 2Gi#6770
Conversation
Updated the memory limits for {{kib}} from 1Gi to 2Gi to ensure sufficient resources for core functionality and prevent service interruptions.
Closes #6581
Elastic Docs AI PR menuCheck the box to run an AI review for this pull request.
Powered by GitHub Agentic Workflows and docs-actions. For more information, reach out to the docs team. |
🔍 Preview links for changed docs |
✅ Elastic Docs Style Checker (Vale)No issues found on modified lines! The Vale linter checks documentation changes against the Elastic Docs style guide. To use Vale locally or report issues, refer to Elastic style guide for Vale. |
|
@shainaraskas , @yetanothertw : how would you address this change? Kibana default memory limit has been increased to 2Gi from 1Gi in ECK 3.4.0, but in earlier versions the default memory limit, if not set explicitly, will still be 1Gi. What's the best way to address this and future changes on this regard? In other docs we have created tabs for version ranges. Would you apply something similar here? |
Yes, I think tabs for version ranges might work the cleanest. But would you have to replicate the entire table twice? You'll be able to tell which way is clearer once you've tried it. That's what I'd do anyway. |
|
|
||
| ::::{note} | ||
| The default 1 Gi {{kib}} limit is sufficient for core functionality. For Platinum and Enterprise users, we recommend at least 2 Gi of memory for each {{kib}} instance. With less than 2 Gi, you can face service interruptions when using features such as Security detection rules, reporting, workflows, and Agent Builder. | ||
| The default 2 Gi {{kib}} limit is sufficient for core functionality. For Platinum and Enterprise users, we recommend at least 2 Gi of memory for each {{kib}} instance. With less than 2 Gi, you can face service interruptions when using features such as Security detection rules, reporting, workflows, and Agent Builder. |
There was a problem hiding this comment.
This sounds a bit weird for me.
The default is 2 Gi, but for specific use cases we recommend 2 Gi.
We should either increase the recommendation, or remove this line from the documentation
There was a problem hiding this comment.
Yes, I agree. Even with the at least it doesn't sound nice.
Thanks for the comment
There was a problem hiding this comment.
@eedugon I added this during the window where the default compute resources were lower.
I think what this actually needs is version-awareness - I assume in older ECK versions, regardless of stack version, the default would be lower? so the default in the table would need two bullets, one for the two states, and then this note would need to be contextualized to older versions.
Awesome, thanks! I've done that but without bullets. Here you have an example showing both options, I think the bullets reduce the consistency with the rest of the table: 
|
4 participants
Updated the default memory limits for {{kib}} from 1Gi to 2Gi.
Closes #6581
Summary
Generative AI disclosure