# Elastic Search v7.17.1 Alias Filtering Performance Issues

**URL:** <https://discuss.elastic.co/t/elastic-search-v7-17-1-alias-filtering-performance-issues/303443>\
**Category:** Elasticsearch\
**Created:** [April 27, 2022, 9:12pm UTC](https://discuss.elastic.co/t/elastic-search-v7-17-1-alias-filtering-performance-issues/303443 "2022-04-27T21:12:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![mma1](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@mma1](https://discuss.elastic.co/u/mma1)\
**Post date:** [April 27, 2022, 9:12pm UTC](https://discuss.elastic.co/t/elastic-search-v7-17-1-alias-filtering-performance-issues/303443/1 "2022-04-27T21:12:14Z")

</div>

Hello,

I have recently started using alias filtering with our application and have seen some performance issues. I am using elastic v7.17.1 on a 12 node cluster.

The alias looks like the following (the array in terms contains 391 items):

```auto
{
  "myIndex" : {
    "aliases" : {
      "myAlias" : {
        "filter" : {
          "bool" : {
            "filter" : {
              "terms" : {
                "code" : [
                  "abc",
                  "xyz",
                  etc...
                ]
              }
            }
          }
        }
      }
    }
  }
}

```

When this new alias is used, I see increased latency and request times on the index:

 ![Screen Shot 2022-04-27 at 16.32.35](https://us1.discourse-cdn.com/elastic/original/3X/c/c/cc721d29519fa9eeceed74b9cc0004314eef4097.png)  
 ![Screen Shot 2022-04-27 at 16.32.31](https://us1.discourse-cdn.com/elastic/original/3X/c/5/c5965330127d1aad60f04814082e4afd83359909.png)

When I revert the change and go back to using a non-filtered alias, the metrics drop back down. Is there anything with this alias filter that would cause an issue with Elasticsearch v7.17.1?

---

<div class="post-metadata">

**Author:** ![mma1](https://avatars.discourse-cdn.com/v4/letter/m/858c86/32.png) [@mma1](https://discuss.elastic.co/u/mma1)\
**Post date:** [April 27, 2022, 9:53pm UTC](https://discuss.elastic.co/t/elastic-search-v7-17-1-alias-filtering-performance-issues/303443/2 "2022-04-27T21:53:28Z")

</div>

I also observed that 4 of the 12 nodes in the cluster had increased CPU utilization and request rates. That seems to be the reason for the overall latency increase, but I am not sure why this filter alias would cause a change like that. The other 8 nodes remained under utilized.

---

<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 25, 2022, 9:53pm UTC](https://discuss.elastic.co/t/elastic-search-v7-17-1-alias-filtering-performance-issues/303443/3 "2022-05-25T21:53:46Z")

</div>

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