# Shard Allocation \_name takes bogus name

**URL:** <https://discuss.elastic.co/t/shard-allocation-name-takes-bogus-name/206681>\
**Category:** Elasticsearch\
**Created:** [November 5, 2019, 10:27pm UTC](https://discuss.elastic.co/t/shard-allocation-name-takes-bogus-name/206681 "2019-11-05T22:27:48Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![naoko](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/naoko/32/11822_2.png) [@naoko](https://discuss.elastic.co/u/naoko)\
**Post date:** [November 5, 2019, 10:27pm UTC](https://discuss.elastic.co/t/shard-allocation-name-takes-bogus-name/206681/1 "2019-11-05T22:27:48Z")

</div>

I want to send a certain index to a set of nodes.  
I see shard allocation filtering seems to be what I need so that different apps (different index) impact set of nodes. I put settings with

`"index.routing.allocation.include._name": "bogus_name"`

and

`"index.routing.allocation.require._name": "bogus_name"`

Although "bogus\_name" nodes do not exist, it allocated shards to some other nodes and moved on. Is this expected behavior?

Thank you

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/elastic/original/3X/1/a/1ac57faf039f6b580b3f104ef42a2a89e41014de.png) [@system](https://discuss.elastic.co/u/system)\
**Post date:** [December 3, 2019, 10:27pm UTC](https://discuss.elastic.co/t/shard-allocation-name-takes-bogus-name/206681/2 "2019-12-03T22:27:50Z")

</div>

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.