# Shard allocation awareness (forced too) and replica allocation **URL:** \ **Category:** Elasticsearch\ **Created:** [May 24, 2013, 9:01pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118 "2013-05-24T21:01:10Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Sebastien\_Coutu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastien_coutu/32/2284_2.png) [@Sebastien\_Coutu](https://discuss.elastic.co/u/Sebastien_Coutu)\ **Post date:** [May 24, 2013, 9:01pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/1 "2013-05-24T21:01:10Z")
Hi everyone, A bit of background: - Cluster of six nodes, three tagged as being "indexers" and three tagged as being "searchers" - One index, three shards, replication of one. I'd like to know if it's possible to have a replication factor of three so all the "searchers" have a replica of all the shards. I've tried it and both the searchers and indexers ended up with two shards each and when I tried to move the replica shards from the "indexers" to the "searchers", elastic returned me the following: {"error":"RemoteTransportException[[node0005][inet[/ip\_address:9301]][cluster/reroute]]; nested: ElasticSearchIllegalArgumentException[[move\_allocation] can't move [hopper][1], from [node0006][KylcDE8ZTL6KfETSMecxzQ][inet[node0006/ip\_address:9301]]{role=index, master=true}, to [node0003][PjcZhF73SxmS8G-wQkSL0A][inet[node0003/ip\_address:9301]]{role=search, master=true}, since its not allowed, reason: [YES()][YES()][YES()][YES()][YES()][NO()][YES()]]; ","status":400} Any ideas? Thanks! Sebastien -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Sebastien\_Coutu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastien_coutu/32/2284_2.png) [@Sebastien\_Coutu](https://discuss.elastic.co/u/Sebastien_Coutu)\ **Post date:** [May 24, 2013, 9:01pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/2 "2013-05-24T21:01:33Z")
By the way, I'm using 0.90.0 🙂 On Friday, May 24, 2013 5:01:10 PM UTC-4, Sebastien Coutu wrote: > Hi everyone, > > A bit of background: > > - Cluster of six nodes, three tagged as being "indexers" and three tagged > as being "searchers" > - One index, three shards, replication of one. > > I'd like to know if it's possible to have a replication factor of three so > all the "searchers" have a replica of all the shards. I've tried it and > both the searchers and indexers ended up with two shards each and when I > tried to move the replica shards from the "indexers" to the "searchers", > elastic returned me the following: > > {"error":"RemoteTransportException[[node0005][inet[/ip\_address:9301]][cluster/reroute]]; > nested: ElasticSearchIllegalArgumentException[[move\_allocation] can't move > [hopper][1], from > [node0006][KylcDE8ZTL6KfETSMecxzQ][inet[node0006/ip\_address:9301]]{role=index, > master=true}, to > [node0003][PjcZhF73SxmS8G-wQkSL0A][inet[node0003/ip\_address:9301]]{role=search, > master=true}, since its not allowed, reason: > [YES()][YES()][YES()][YES()][YES()][NO()][YES()]]; ","status":400} > > Any ideas? > > Thanks! > > Sebastien -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [May 25, 2013, 6:35am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/3 "2013-05-25T06:35:28Z")
Are you saying that the searchers have no shards? Both primaries and replicas are on the indexers? Please post your config (and any index settings) -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![simonw\_2](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/simonw_2/32/1130_2.png) [@simonw\_2](https://discuss.elastic.co/u/simonw_2)\ **Post date:** [May 25, 2013, 6:39am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/4 "2013-05-25T06:39:04Z")
some factors in the allocation decision prevent a move of a shard here, can you tell what kind of setting you have aside of the defaults related to allocation and the number of machines ie. your setup? simon On Friday, May 24, 2013 11:01:33 PM UTC+2, Sebastien Coutu wrote: > By the way, I'm using 0.90.0 🙂 > > On Friday, May 24, 2013 5:01:10 PM UTC-4, Sebastien Coutu wrote: > > > Hi everyone, > > > > A bit of background: > > > > - Cluster of six nodes, three tagged as being "indexers" and three tagged > > as being "searchers" > > - One index, three shards, replication of one. > > > > I'd like to know if it's possible to have a replication factor of three > > so all the "searchers" have a replica of all the shards. I've tried it and > > both the searchers and indexers ended up with two shards each and when I > > tried to move the replica shards from the "indexers" to the "searchers", > > elastic returned me the following: > > > > {"error":"RemoteTransportException[[node0005][inet[/ip\_address:9301]][cluster/reroute]]; > > nested: ElasticSearchIllegalArgumentException[[move\_allocation] can't move > > [hopper][1], from > > [node0006][KylcDE8ZTL6KfETSMecxzQ][inet[node0006/ip\_address:9301]]{role=index, > > master=true}, to > > [node0003][PjcZhF73SxmS8G-wQkSL0A][inet[node0003/ip\_address:9301]]{role=search, > > master=true}, since its not allowed, reason: > > [YES()][YES()][YES()][YES()][YES()][NO()][YES()]]; ","status":400} > > > > Any ideas? > > > > Thanks! > > > > Sebastien -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Sebastien\_Coutu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastien_coutu/32/2284_2.png) [@Sebastien\_Coutu](https://discuss.elastic.co/u/Sebastien_Coutu)\ **Post date:** [May 27, 2013, 2:30pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/5 "2013-05-27T14:30:43Z")
Hi Clinton, Actually, what I'm saying is that I'd like every searcher to have a replica of every shard. Right now, when I have primaries + 1 set of replicas, it acts as I'd expect which is all the primaries on the "indexers" and all the replicas on the "searchers". When I change the number of replicas to 3 (I have 3 search hosts) so all my search hosts get a replica, two replicas end up on the search hosts and 1 replica end up with the primaries on the "indexers". Here's a sample config: For searchers: cluster.name: "mycluster" node.name: ${HOSTNAME} node.master: true node.data: true _node.role: search_ path.conf: /etc/elastic/conf path.data: /app/elastic/data path.work: /app/elastic/work path.logs: /app/elastic/logs path.plugins: /app/elastic/plugins bootstrap.mlockall: true transport.tcp.port: 9301 http.port: 9201 discovery.zen.minimum\_master\_nodes: 3 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["node0004:9301", "node0005:9301", "node0006:9301"] _cluster.routing.allocation.awareness.attributes: role_ _cluster.routing.allocation.awareness.force.role.values: index,search_ index.number\_of\_shards: 3 index.number\_of\_replicas: 1 For indexers: cluster.name: "mycluster" node.name: ${HOSTNAME} node.master: true node.data: true _node.role: index_ path.conf: /etc/elastic/conf path.data: /app/elastic/data path.work: /app/elastic/work path.logs: /app/elastic/logs path.plugins: /app/elastic/plugins bootstrap.mlockall: true transport.tcp.port: 9301 http.port: 9201 discovery.zen.minimum\_master\_nodes: 3 discovery.zen.ping.multicast.enabled: false discovery.zen.ping.unicast.hosts: ["node0004:9301", "node0005:9301", "node0006:9301"] _cluster.routing.allocation.awareness.attributes: role_ _cluster.routing.allocation.awareness.force.role.values: index,search_ index.number\_of\_shards: 3 index.number\_of\_replicas: 1 Thanks for the help! Sebastien On Sat, May 25, 2013 at 2:35 AM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > Are you saying that the searchers have no shards? Both primaries and > replicas are on the indexers? > > Please post your config (and any index settings) > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US) > . > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Sebastien\_Coutu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastien_coutu/32/2284_2.png) [@Sebastien\_Coutu](https://discuss.elastic.co/u/Sebastien_Coutu)\ **Post date:** [May 27, 2013, 2:35pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/6 "2013-05-27T14:35:46Z")
Hi Simon, The configuration is pretty vanilla except the forced allocation awareness. 6 nodes from which 3 of them have the "role" of "search" and 3 of them have the role of "index". I'm planning on pointing the "indexing clients" to the index machines and "search clients" to the search machines. Thanks! Sebastien On Sat, May 25, 2013 at 2:39 AM, simonw [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)wrote: > some factors in the allocation decision prevent a move of a shard here, > can you tell what kind of setting you have aside of the defaults related to > allocation and the number of machines ie. your setup? > > simon > > On Friday, May 24, 2013 11:01:33 PM UTC+2, Sebastien Coutu wrote: > > > By the way, I'm using 0.90.0 🙂 > > > > On Friday, May 24, 2013 5:01:10 PM UTC-4, Sebastien Coutu wrote: > > > > > Hi everyone, > > > > > > A bit of background: > > > > > > - Cluster of six nodes, three tagged as being "indexers" and three > > > tagged as being "searchers" > > > - One index, three shards, replication of one. > > > > > > I'd like to know if it's possible to have a replication factor of three > > > so all the "searchers" have a replica of all the shards. I've tried it and > > > both the searchers and indexers ended up with two shards each and when I > > > tried to move the replica shards from the "indexers" to the "searchers", > > > elastic returned me the following: > > > > > > {"error":"\*\*RemoteTransportException[[\*\*node0005][inet[/ip\_address:**9301]][cluster/reroute]]; > > > nested: ElasticSearchIllegalArgumentEx**ception[[move\_allocation] can't > > > move [hopper][1], from [node0006][**KylcDE8ZTL6KfETSMecxzQ][inet[** > > > node0006/ip\_address:9301]]{\*\*role=index, master=true}, to > > > [node0003][PjcZhF73SxmS8G-\*\*wQkSL0A][inet[node0003/ip\_\*\*address:9301]]{role=search, > > > master=true}, since its not allowed, reason: [YES()][YES()][YES()][YES()][ > > > \*\*YES()][NO()][YES()]]; ","status":400} > > > > > > Any ideas? > > > > > > Thanks! > > > > > > Sebastien > > > > -- > > You received this message because you are subscribed to a topic in the > > Google Groups "elasticsearch" group. > > To unsubscribe from this topic, visit > > [https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US) > > . > > To unsubscribe from this group and all its topics, send an email to > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Clinton\_Gormley](https://avatars.discourse-cdn.com/v4/letter/c/50afbb/32.png) [@Clinton\_Gormley](https://discuss.elastic.co/u/Clinton_Gormley)\ **Post date:** [May 28, 2013, 3:12pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/7 "2013-05-28T15:12:27Z")
Sebastien, primary and replica shards are identical. When you index a document, it hits the primary first, then the replicas after that. So all shards are indexing shards. Separating primaries and replicas like this is artificial and won't do what you hope On 27 May 2013 16:35, Sebastien Coutu [scoutu@hopper.com](mailto:scoutu@hopper.com) wrote: > Hi Simon, > > The configuration is pretty vanilla except the forced allocation > awareness. 6 nodes from which 3 of them have the "role" of "search" and 3 > of them have the role of "index". I'm planning on pointing the "indexing > clients" to the index machines and "search clients" to the search machines. > > Thanks! > > Sebastien > > On Sat, May 25, 2013 at 2:39 AM, simonw \<[simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com) > > > wrote: > > > some factors in the allocation decision prevent a move of a shard here, > > can you tell what kind of setting you have aside of the defaults related to > > allocation and the number of machines ie. your setup? > > > > simon > > > > On Friday, May 24, 2013 11:01:33 PM UTC+2, Sebastien Coutu wrote: > > > > > By the way, I'm using 0.90.0 🙂 > > > > > > On Friday, May 24, 2013 5:01:10 PM UTC-4, Sebastien Coutu wrote: > > > > > > > Hi everyone, > > > > > > > > A bit of background: > > > > > > > > - Cluster of six nodes, three tagged as being "indexers" and three > > > > tagged as being "searchers" > > > > - One index, three shards, replication of one. > > > > > > > > I'd like to know if it's possible to have a replication factor of three > > > > so all the "searchers" have a replica of all the shards. I've tried it and > > > > both the searchers and indexers ended up with two shards each and when I > > > > tried to move the replica shards from the "indexers" to the "searchers", > > > > elastic returned me the following: > > > > > > > > {"error":"\*\*RemoteTransportException[[\*\*node0005][inet[/ip\_address:**9301]][cluster/reroute]]; > > > > nested: ElasticSearchIllegalArgumentEx**ception[[move\_allocation] > > > > can't move [hopper][1], from [node0006][\*\*KylcDE8ZTL6KfETSMecxzQ][inet[ > > > > \*\*node0006/ip\_address:9301]]{\*\*role=index, master=true}, to > > > > [node0003][PjcZhF73SxmS8G-\*\*wQkSL0A][inet[node0003/ip\_\*\*address:9301]]{role=search, > > > > master=true}, since its not allowed, reason: [YES()][YES()][YES()][YES()][ > > > > \*\*YES()][NO()][YES()]]; ","status":400} > > > > > > > > Any ideas? > > > > > > > > Thanks! > > > > > > > > Sebastien > > > > > > -- > > > You received this message because you are subscribed to a topic in the > > > Google Groups "elasticsearch" group. > > > To unsubscribe from this topic, visit > > > [https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US) > > > . > > > To unsubscribe from this group and all its topics, send an email to > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to the Google Groups > "elasticsearch" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![Sebastien\_Coutu](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/sebastien_coutu/32/2284_2.png) [@Sebastien\_Coutu](https://discuss.elastic.co/u/Sebastien_Coutu)\ **Post date:** [May 28, 2013, 3:40pm UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/8 "2013-05-28T15:40:11Z")
Hi Clinton, So I guess it's also a bad idea to have different tuning configuration for the machines in the "search" and on the "index" groups? Thanks, Sebastien On Tue, May 28, 2013 at 11:12 AM, Clinton Gormley [clint@traveljury.com](mailto:clint@traveljury.com)wrote: > Sebastien, primary and replica shards are identical. When you index a > document, it hits the primary first, then the replicas after that. So all > shards are indexing shards. > > Separating primaries and replicas like this is artificial and won't do > what you hope > > On 27 May 2013 16:35, Sebastien Coutu [scoutu@hopper.com](mailto:scoutu@hopper.com) wrote: > > > Hi Simon, > > > > The configuration is pretty vanilla except the forced allocation > > awareness. 6 nodes from which 3 of them have the "role" of "search" and 3 > > of them have the role of "index". I'm planning on pointing the "indexing > > clients" to the index machines and "search clients" to the search machines. > > > > Thanks! > > > > Sebastien > > > > On Sat, May 25, 2013 at 2:39 AM, simonw \< > > [simon.willnauer@elasticsearch.com](mailto:simon.willnauer@elasticsearch.com)\> wrote: > > > > > some factors in the allocation decision prevent a move of a shard here, > > > can you tell what kind of setting you have aside of the defaults related to > > > allocation and the number of machines ie. your setup? > > > > > > simon > > > > > > On Friday, May 24, 2013 11:01:33 PM UTC+2, Sebastien Coutu wrote: > > > > > > > By the way, I'm using 0.90.0 🙂 > > > > > > > > On Friday, May 24, 2013 5:01:10 PM UTC-4, Sebastien Coutu wrote: > > > > > > > > > Hi everyone, > > > > > > > > > > A bit of background: > > > > > > > > > > - Cluster of six nodes, three tagged as being "indexers" and three > > > > > tagged as being "searchers" > > > > > - One index, three shards, replication of one. > > > > > > > > > > I'd like to know if it's possible to have a replication factor of > > > > > three so all the "searchers" have a replica of all the shards. I've tried > > > > > it and both the searchers and indexers ended up with two shards each and > > > > > when I tried to move the replica shards from the "indexers" to the > > > > > "searchers", elastic returned me the following: > > > > > > > > > > {"error":"\*\*RemoteTransportException[[**node0005][inet[/ip\_address:9301]][cluster/reroute]]; > > > > > nested: ElasticSearchIllegalArgumentException[[move\_allocation] > > > > > can't move [hopper][1], from [node0006][** > > > > > KylcDE8ZTL6KfETSMecxzQ][inet[\*\*node0006/ip\_address:9301]]{**role=index, > > > > > master=true}, to [node0003][PjcZhF73SxmS8G-** > > > > > wQkSL0A][inet[node0003/ip\_\*\*address:9301]]{role=search, master=true}, > > > > > since its not allowed, reason: [YES()][YES()][YES()][YES()][\*\*YES()][NO()][YES()]]; > > > > > ","status":400} > > > > > > > > > > Any ideas? > > > > > > > > > > Thanks! > > > > > > > > > > Sebastien > > > > > > > > -- > > > > You received this message because you are subscribed to a topic in the > > > > Google Groups "elasticsearch" group. > > > > To unsubscribe from this topic, visit > > > > [https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US) > > > > . > > > > To unsubscribe from this group and all its topics, send an email to > > > > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > > > -- > > You received this message because you are subscribed to the Google Groups > > "elasticsearch" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > > > > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). > > -- > You received this message because you are subscribed to a topic in the > Google Groups "elasticsearch" group. > To unsubscribe from this topic, visit > [https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US](https://groups.google.com/d/topic/elasticsearch/HEzxX0bnPoo/unsubscribe?hl=en-US) > . > To unsubscribe from this group and all its topics, send an email to > [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). > For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). -- You received this message because you are subscribed to the Google Groups "elasticsearch" group. To unsubscribe from this group and stop receiving emails from it, send an email to [elasticsearch+unsubscribe@googlegroups.com](mailto:elasticsearch+unsubscribe@googlegroups.com). For more options, visit [https://groups.google.com/groups/opt\_out](https://groups.google.com/groups/opt_out). ---
**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\ **Post date:** [July 6, 2017, 2:34am UTC](https://discuss.elastic.co/t/shard-allocation-awareness-forced-too-and-replica-allocation/12118/9 "2017-07-06T02:34:19Z")