We are shipping server events using filebeat and metrics using metricbeat to our Elastic Cloud cluster that has a hot server and a warm server. The cluster is set up with no redundancy, ie just a single hot and a single warm node.
Both metricbeat and filebeat have the same ILM profile - that is to roll over from hot to warm at 40GB. Metricbeat and filebeat are both rolling over OK, but for some reason the filebeat index gets duplicated and the storage becomes 80G when on warm. I also see the status as "green" which usually means that the index is replicated.
How do I prevent the filebeat index from replicating when it rolls over?