Review the following information about the Kibana 8.8.1 release.
Kibana can run out of memory during an upgrade when there are many Fleet agent policies.
Due to a schema version update, during Fleet setup in 8.8.x, all agent policies are being queried and deployed. This action triggers a lot of queries to the Elastic Package Registry (EPR) to fetch integration packages. As a result, there is an increase in Kibana’s resident memory usage (RSS).
Because the default batch size of
100 for schema version upgrade of Fleet agent policies is too high, this can
cause Kibana to run out of memory during an upgrade. For example, we have observed 1GB Kibana instances run
out of memory during an upgrade when there were 20 agent policies with 5 integrations in each.
Two workaround options are available:
- Increase the Kibana instance size to 2GB. So far, we are not able to reproduce the issue with 2GB instances.
kibana.ymland restart the Kibana instance(s).
In 8.9.0, we are addressing this by changing the default batch size to
Memory leak in Fleet audit logging.
Fleet introduced audit logging for various CRUD (create, read, update, and delete) operations in version 8.8.0.
While audit logging is not enabled by default, we have identified an off-heap memory leak in the implementation of Fleet audit logging that can result in poor Kibana performance, and in some cases Kibana instances being terminated by the OS kernel’s oom-killer. This memory leak can occur even when Kibana audit logging is not explicitly enabled (regardless of whether
xpack.security.audit.enabled is set in the
kibana.yml settings file).
The version 8.8.2 release includes in a fix for this problem. If you are using Fleet integrations and Kibana audit logging in version 8.8.0 or 8.8.1, you should upgrade to 8.8.2 or above to obtain the fix.
Breaking changes can prevent your application from optimal operation and performance. Before you upgrade to 8.8.1, review the breaking changes, then mitigate the impact to your application.
There are no breaking changes in the Kibana 8.8.1 release.
To review the breaking changes in the previous release, check 8.8.0.
- Elastic Security
- For the Elastic Security 8.8.1 release information, refer to Elastic Security Solution Release Notes.
- Include hidden data streams in package upgrade #158654
- Fixes Log Categorization UI failure due to an infinite loop #159090
- Machine Learning
- Fixes configuration stacking order #158827
- Fixes Kibana crashing on Safari versions prior to 16.4 #158825
Updates all aliases with a single
updateAliases()when relocating saved objects #158940
- Fixes a race condition that could cause intermittent upgrade migration failures when Kibana connects to a single node Elasticsearch cluster #158182
Dynamically reduces the
migrations.batchSizevalue when Kibana encounters a migration batch that’s too big to process #157494