# Cluster shard allocation filtering doesn't affect primary shards

**URL:** <https://discuss.elastic.co/t/cluster-shard-allocation-filtering-doesnt-affect-primary-shards/83621>\
**Category:** Elasticsearch\
**Created:** [April 25, 2017, 10:41pm UTC](https://discuss.elastic.co/t/cluster-shard-allocation-filtering-doesnt-affect-primary-shards/83621 "2017-04-25T22:41:49Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![f-w](https://avatars.discourse-cdn.com/v4/letter/f/4af34b/32.png) [@f-w](https://discuss.elastic.co/u/f-w)\
**Post date:** [April 25, 2017, 10:41pm UTC](https://discuss.elastic.co/t/cluster-shard-allocation-filtering-doesnt-affect-primary-shards/83621/1 "2017-04-25T22:41:49Z")

</div>

On ES 2.4.3, applying cluster shard filtering such as the one below only moves replica shards to other nodes. Primary ones got stuck on the node. Is this a bug or by design?

> PUT /\_cluster/settings  
> {  
> "transient" : {  
> "cluster.routing.allocation.exclude.\_ip" : "10.0.0.1"  
> }  
> }

---

<div class="post-metadata">

**Author:** ![f-w](https://avatars.discourse-cdn.com/v4/letter/f/4af34b/32.png) [@f-w](https://discuss.elastic.co/u/f-w)\
**Post date:** [April 25, 2017, 11:07pm UTC](https://discuss.elastic.co/t/cluster-shard-allocation-filtering-doesnt-affect-primary-shards/83621/2 "2017-04-25T23:07:15Z")

</div>

found out it's due to rolling upgrade from 2.4.3 to 2.4.4

---

<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:** [May 23, 2017, 11:21pm UTC](https://discuss.elastic.co/t/cluster-shard-allocation-filtering-doesnt-affect-primary-shards/83621/3 "2017-05-23T23:21:05Z")

</div>

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