Hello, with reference to 7.10 and https://www.elastic.co/guide/en/elasticsearch/reference/master/data-tiers.html
Content tier nodes are usually optimized for query performance—they prioritize processing power over IO throughput so they can process complex searches and aggregations and return results quickly. While they are also responsible for indexing, content data is generally not ingested at as high a rate as time series data such as logs and metrics. From a resiliency perspective the indices in this tier should be configured to use one or more replicas.
When you create an index, by default Elasticsearch sets
data_contentto automatically allocate the index shards to the content tier.
So I do not have "content_tier" applied to my cold nodes
however ILM is failing to allocate shards to the cold nodes because all indecies have the tier_preference to content.
Not sure what is the right way to fix this. I want all new data to go to hot these have
node.roles: ["ingest", "data_hot", "data_content" ]
cold nodes have
The instructions seem to imply that cold nodes both should not have data_content and must have data_content.