# How to continuously keep indexing and querying in ES

**URL:** <https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [February 27, 2019, 4:40pm UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206 "2019-02-27T16:40:24Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Karthik\_K\_G](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@Karthik\_K\_G](https://discuss.elastic.co/u/Karthik_K_G)\
**Post date:** [February 27, 2019, 4:40pm UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206/1 "2019-02-27T16:40:24Z")

</div>

Hi team,

I am trying to run Rally to continuously index and query, but I see that all the challenges are limited to the documents or the size. Is there a way or a repository with the track to run the test for a long run. Suppose I am having a server with 128GB RAM, I would like to index upto 1.5 TB or more and also have read traffic. Is this possible with Rally, if yes what would be my ideal track and challenge for this scenario.  
I found a git repo with similar kind of challenges, but there is no challenge with continuous indexing [https://github.com/elastic/rally-eventdata-track](https://github.com/elastic/rally-eventdata-track)  
Can anyone help here.

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 27, 2019, 4:48pm UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206/2 "2019-02-27T16:48:11Z")

</div>

As the dventdata track generates data you can create challenges that run concurrent indexing and querying over long time periods. I have used it to create challenges that have run for days.

---

<div class="post-metadata">

**Author:** ![Karthik\_K\_G](https://avatars.discourse-cdn.com/v4/letter/k/fbc32d/32.png) [@Karthik\_K\_G](https://discuss.elastic.co/u/Karthik_K_G)\
**Post date:** [February 27, 2019, 10:07pm UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206/3 "2019-02-27T22:07:57Z")

</div>

@Christian_Dahlqvist:

Is there a challenge that I can use here, which is already present ? Similar to something here [https://github.com/elastic/rally-eventdata-track](https://github.com/elastic/rally-eventdata-track)

---

<div class="post-metadata">

**Author:** ![Christian\_Dahlqvist](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/christian_dahlqvist/32/4617_2.png) [@Christian\_Dahlqvist](https://discuss.elastic.co/u/Christian_Dahlqvist)\
**Post date:** [February 28, 2019, 6:37am UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206/4 "2019-02-28T06:37:55Z")

</div>

I would recommend creating your own challenge that is adjusted to fit the size and expected traffic of your cluster. It would be a good example to add to the event data track but does as far as I remember not currently exist.

---

<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:** [March 28, 2019, 6:37am UTC](https://discuss.elastic.co/t/how-to-continuously-keep-indexing-and-querying-in-es/170206/5 "2019-03-28T06:37:57Z")

</div>

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