The following limitations and known problems apply to the 1.1.4 release of ECE:
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 clusters might not get created on the allocator. To resolve this issue, see Allocators Are Not Being Used.
- 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.
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.
- Pending plan changes for your cluster in the Cloud UI that would exceed 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.)
- X-Pack monitoring features and Marvel can be used only to send monitoring data between Elasticsearch clusters that are running the same version.
- 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.
Changing the generated password for the
adminuser on the administration console cluster that backs the Cloud UI is not supported. This is the
adminuser on the
admin-console-elasticsearchcluster that gets created during the ECE installation.
Do not change the generated password for the
adminuser on the administration console cluster or you risk losing administrative access to your cluster.
Some additional limitations apply when securing your installation. To learn more, see Secure Elastic Cloud Enterprise.