# Cross cluster search and index wildcards (elastic 6.6.x)

**URL:** <https://discuss.elastic.co/t/cross-cluster-search-and-index-wildcards-elastic-6-6-x/187540>\
**Category:** Elasticsearch\
**Created:** [June 26, 2019, 10:15am UTC](https://discuss.elastic.co/t/cross-cluster-search-and-index-wildcards-elastic-6-6-x/187540 "2019-06-26T10:15:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![trocade](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/trocade/32/100338_2.png) [@trocade](https://discuss.elastic.co/u/trocade)\
**Post date:** [June 26, 2019, 10:15am UTC](https://discuss.elastic.co/t/cross-cluster-search-and-index-wildcards-elastic-6-6-x/187540/1 "2019-06-26T10:15:40Z")

</div>

So I am playing around a little with wildcards in our cluster setup (1 ccs, 3 data cluster)

When I do cross-cluster searches on indexes using wildcards I am a bit curious of the behavior.

Let's say we have 6 months of data which is divided into aliases time/size based indices.

If I do this search (replace the month with anything from 01 to 06)

`GET /*:myindex-2019.06.*/_search` it takes ~1 second

But this search takes about 30 seconds, but based on the initial search the logical would be a maximum of 10s with some overhead.  
`GET /*:myindex-2019.*/_search`

is there a logic behind that the second wildcards become so expensive?

---

<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 24, 2019, 10:15am UTC](https://discuss.elastic.co/t/cross-cluster-search-and-index-wildcards-elastic-6-6-x/187540/2 "2019-07-24T10:15:41Z")

</div>

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