# Reroute API - Node does not match index include filters

**URL:** <https://discuss.elastic.co/t/reroute-api-node-does-not-match-index-include-filters/20193>\
**Category:** Elasticsearch\
**Created:** [October 10, 2014, 10:13pm UTC](https://discuss.elastic.co/t/reroute-api-node-does-not-match-index-include-filters/20193 "2014-10-10T22:13:32Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Shyam](https://avatars.discourse-cdn.com/v4/letter/s/dfb087/32.png) [@Shyam](https://discuss.elastic.co/u/Shyam)\
**Post date:** [October 10, 2014, 10:13pm UTC](https://discuss.elastic.co/t/reroute-api-node-does-not-match-index-include-filters/20193/1 "2014-10-10T22:13:32Z")

</div>

I'm having trouble with my cluster in that it seems only 3 of my nodes (out  
of 5) are being utilized for primary shards. All replica shards remain  
unassigned also.

In trying to resolve the issue I tried using the Reroute API however it  
gives me the following error (with explain on):

## explanations: [1] 0: { command: "allocate" parameters: { index: "group7to11poc" shard: 7 node: "SPOCNODE5" allow\_primary: true }- decisions: [11] 0: { decider: "same\_shard" decision: "YES" explanation: "shard is not allocated to same node or host" }- 1: { decider: "filter" decision: "NO" explanation: "node does not match index include filters [\_id:"4rZYPBOGRMK4y9YG6p7E2w"]" }- 2: { decider: "replica\_after\_primary\_active" decision: "YES" explanation: "primary is already active" }- 3: { decider: "throttling" decision: "YES" explanation: "below shard recovery limit of [2]" }- 4: { decider: "enable" decision: "YES" explanation: "allocation disabling is ignored" }- 5: { decider: "disable" decision: "YES" explanation: "allocation disabling is ignored" }- 6: { decider: "awareness" decision: "YES" explanation: "no allocation awareness enabled" }- 7: { decider: "shards\_limit" decision: "YES" explanation: "total shard limit disabled: [-1] \<= 0" }- 8: { decider: "node\_version" decision: "YES" explanation: "target node version [1.3.2] is same or newer than source node version [1.3.2]" }- 9: { decider: "disk\_threshold" decision: "YES" explanation: "disk usages unavailable" }- 10: { decider: "snapshot\_in\_progress" decision: "YES" explanation: "shard not primary or relocation disabled" }-

## }-

I can see only one NO on there which I have highlighted. I have tried  
running the following on my nodes but it makes no difference:

{  
"index.routing.allocation.include.\_id" : "4rZYPBOGRMK4y9YG6p7E2w"  
}

Any ideas what could be up? I also tried disabling replicas and then  
enabling but they just go straight to unassigned. Even with 3 nodes, the  
replicas should get assigned no? (I'm not sure why the other two are no  
participating, they seem to be accepting Indicies from Marvel with no  
issues so are active in the cluster).

Thanks in advance!

--  
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).  
To view this discussion on the web visit [https://groups.google.com/d/msgid/elasticsearch/8e168beb-525c-4142-b012-3b24e1d4e9c7%40googlegroups.com](https://groups.google.com/d/msgid/elasticsearch/8e168beb-525c-4142-b012-3b24e1d4e9c7%40googlegroups.com).  
For more options, visit [https://groups.google.com/d/optout](https://groups.google.com/d/optout).

---

<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:** [July 6, 2017, 12:56am UTC](https://discuss.elastic.co/t/reroute-api-node-does-not-match-index-include-filters/20193/2 "2017-07-06T00:56:54Z")

</div>