The following limitations and known problems apply to the 2.10.0 release of ECE, or to earlier releases as noted.
For troubleshooting help, you can also refer to the list of Common issues.
Installation and configurationedit
When you install Elastic Cloud Enterprise on a new host and assign it the allocator role from the command line with the
--roles "allocator"parameter during installation, new deployments might not get created on the allocator. To resolve this issue, see Allocators Are Not Being Used.
Some change management tools that auto-reload firewall rules can cause networking issues. Specifically, Docker networking can fail on new containers after restarting the
iptablesservice. To avoid networking failures, disable the automatic reloading of firewall rules.
- On RHEL and CentOS, the firewalld service is not compatible with Docker and interferes with the installation of ECE. You must disable firewalld before installing or reinstalling ECE.
- When you use OverlayFS with Kernel-LT 4.4.156 and later, there is a known regression that prevents Elastic Cloud Enterprise from completing the installation. From the kernel-archive, use Kernel 4.4.155.
- If you install ECE on AWS, you likely need to modify the cluster endpoint, as the public hostname resolves to a different IP address externally than it does internally on the cluster.
- ECE is unable to support VMotion functionality in VMWare. To use ECE, you must disable VMotion.
- When you use virtualization resources, make sure that you avoid resource overallocation.
Due to a known Elasticsearch bug, plans for Elasticsearch versions 7.7.0 and 7.7.1 can fail unexpectedly with an error that indicates that there was a bad request while performing the constructor’s step
validate-enough-disk-space. To resolve this, first try manually restarting all nodes of the cluster. If restarting doesn’t resolve the problem, you can edit the cluster plan to set the
true. We also recommend upgrading to version 7.8 or higher, which resolves this bug. For more details, see the version 2.2.2 release notes.
Changing the generated password for the
adminuser on the administration console deployment that backs the Cloud UI is not supported. This is the
adminuser on the
admin-console-elasticsearchdeployment that gets created during the ECE installation.
Do not change the generated password for the
adminuser on the administration console deployment or you risk losing administrative access to your installation.
When configuring Elastic Cloud Enterprise role-based access control:
- Trying to use an invalid SAML provider can cause the security deployment to bootloop. The deployment falls back to the previous configuration, but if there are any issues between the UI and the actual configuration, remove or update the SAML provider profile. If the problem persists, review the deployment activity and logs.
- PEM and PKCS11 formatted certificates are not supported.
Some additional limitations apply when securing your installation. To learn more, see Secure Elastic Cloud Enterprise.
- Pending plan changes for your deployment in the Cloud UI that exceed the available capacity will fail as expected, but might then require you to manually recover from the failure. (To recover, locate the details for the plan attempt and copy the diff; manually edit the diff to revert to the original plan and apply the modified plan into the Advanced cluster configuration panel.)
- ECE has a maximum limit of 420 seconds, so we recommend optimizing long-running queries in Elasticsearch.
- A known issue can prevent direct rolling upgrades from Elasticsearch version 5.6.10 to version 6.3.0. As a workaround, we have removed version 6.3.0 from the Cloud UI for new cluster deployments and for upgrading existing ones. If you are affected by this issue, see Rolling upgrades from 5.6.x to 6.3.0 fails with "java.lang.IllegalStateException: commit doesn’t contain history uuid" in our Elastic Support Portal. If these steps do not work or you do not have access to the Support Portal, you can contact email@example.com.
- If upgrading from a version earlier than 2.1.0 to a version between >2.1.0 and ⇐2.3.1, a known problem will fail the upgrade. If your upgrade path matches these versions, see Before upgrading check your upgrade path.
- When upgrading to 2.4.0, make sure that nothing listens on your proxy node over port 9000. If a Minio repository runs on the same ECE node, you’ll need to change the default listening port. If there is a port conflict, proxy fails and won’t boot.
Starting with ECE version 2.6.0, deployment upgrades initiated from the UI can fail if there is no healthy instance of Kibana available. As a workaround, you can perform an advanced edit on the cluster to upgrade the cluster version. In the cluster configuration, each occurrence of
elasticsearch.versioncan be updated to the version that you choose. For details, see Advanced cluster configuration.
When upgrading to ECE version 2.7.0 the automatic upgrade of the
admin-console-elasticsearchcluster may fail, particularly on older installations of ECE that started with a 5.x cluster. If this happens, it is safe to leave the cluster at the latest 6.x Elasticsearch version until the automatic upgrade is fixed in the next version of ECE. Note that the
logging-and-metricscluster should also remain on 6.x, only the
securitycluster should be upgraded to the latest 7.x Elasticsearch version using the dedicated API.
The transport client is not considered thread safe in a cloud environment. We recommend that you use the Java REST client instead. This restriction relates to the fact that your deployments hosted on Elastic Cloud Enterprise are behind proxies, which prevent the transport client from communicating directly with Elasticsearch clusters.