# Absurd behaviour in ES Cluster while using aliases

**URL:** <https://discuss.elastic.co/t/absurd-behaviour-in-es-cluster-while-using-aliases/103020>\
**Category:** Elasticsearch\
**Created:** [October 6, 2017, 1:37pm UTC](https://discuss.elastic.co/t/absurd-behaviour-in-es-cluster-while-using-aliases/103020 "2017-10-06T13:37:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Yashpal\_Singh](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/yashpal_singh/32/43209_2.png) [@Yashpal\_Singh](https://discuss.elastic.co/u/Yashpal_Singh)\
**Post date:** [October 6, 2017, 1:37pm UTC](https://discuss.elastic.co/t/absurd-behaviour-in-es-cluster-while-using-aliases/103020/1 "2017-10-06T13:37:44Z")

</div>

We have 3 node cluster namely  
node\_1, node\_2 and node\_3.

Have Created 3 indexes namely  
Index A, B and C.

Config  
node\_1 index A  
node\_2 index B  
node\_3 index c

Have created 3 aliased namely  
X -\> A  
y -\>A,B  
z -\>A,B,C

Have created 3 tcp client namely  
TCP\_X,TCP\_Y and TCP\_Z.  
nodes ip used for init  
TCP\_X -\> node\_1  
TCP\_Y -\> node\_2  
TCP\_Z -\> node\_3

**when node\_3 is down.**  
Observation:  
1)Query using TCP\_Y Client on index y(Alias which points to index A and B)  
a)count call is working fine.  
b)Search call is getting timed\_out.

Could you please let us know what have I done wrong if any?

When I am not quering on the index/alias associated with node3 why it is affecting other queries?

---

<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:** [November 3, 2017, 1:37pm UTC](https://discuss.elastic.co/t/absurd-behaviour-in-es-cluster-while-using-aliases/103020/2 "2017-11-03T13:37:46Z")

</div>

Closed on November 3, 2017, 1:37pm UTC

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