I have a cluster where I am running multiple es nodes on a single server. The cluster is composed of 16 servers, each running 4 es nodes. Are there any shard or index allocation awareness switches that would prevent multiple primary shards from living on the same server?
In other words, I'd like to tag the es nodes running on a server and make sure that only 1 primary shard is allocated to one of the es nodes on a server. The other es nodes on that server could contain replicas but not other primary shards.
I am seeing performance issues when bulk indexing a fairly large request, 10 mb, to an index that has multiple primary shards on a server. The performance of the server hosting the multiple primary shards degrades. I would like to balance my shards more evenly for an index across the different hardware in the cluster. An index has 5 shards and 1 replica.