Version is outdated
The cluster runs an Elasticsearch version that is no longer supported. Without security patches, the cluster is exposed to known vulnerabilities.
For a complete list of insights, refer to AutoOps insights.
| Field | Value |
|---|---|
| Component | Elasticsearch |
| Severity | High |
| Scope | Cluster |
| Domains | version-upgrade |
The following is an example of what you might see when this insight is triggered. Real insights use live data and links from your deployment or cluster.
The cluster runs 8.15.0. The recommended version is 9.5.0.
The following open events are known to stall or fail upgrades. Resolve them before you upgrade. That list is not exhaustive.
Disk watermark flood stage
Deployment not highly available
AutoOps shows different recommendations depending on how their conditions match your deployment or cluster.
Resolve open events before you upgrade
Condition: Shown when upgrade-related events are open.
These open events are known to stall or fail upgrades. Open the list and resolve each event before you upgrade. Also review Watcher, old system indices, and the other preparation steps in the upgrade guide.
Upgrade Elasticsearch
Condition: Always shown for this insight.
Upgrade to the latest minor of your current major before moving to 9.5.0.
Running an unsupported Elasticsearch version means the cluster no longer receives security patches, bug fixes, or compatibility updates. Known vulnerabilities go unaddressed, increasing exposure to security threats. Supported versions benefit from performance and stability improvements that unsupported releases do not receive. Newer releases also include storage and efficiency work, such as better compression, that can reduce the resources a cluster needs for the same workload.
Staying on an unsupported version narrows future upgrade options. Elastic upgrade paths require moving through the latest minor of the current major before crossing a major version boundary.