# IO / Disc "tear down" for elastic search

**URL:** <https://discuss.elastic.co/t/io-disc-tear-down-for-elastic-search/248013>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [September 9, 2020, 1:33pm UTC](https://discuss.elastic.co/t/io-disc-tear-down-for-elastic-search/248013 "2020-09-09T13:33:41Z")\
**Posts on this page:** 1\
**Showing post:** 7

<div class="post-metadata">

**Author:** ![dliappis](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/dliappis/32/56174_2.png) [@dliappis](https://discuss.elastic.co/u/dliappis)\
**Post date:** [September 10, 2020, 9:37am UTC](https://discuss.elastic.co/t/io-disc-tear-down-for-elastic-search/248013/7 "2020-09-10T09:37:34Z")

</div>

> [@Oleg\_Ruchovets](#):
>
> esrally --track=eventdata --track-repository=eventdata --track-params=bulk\_size:10000,bulk\_indexing\_clients:16 --target-hosts=my\_ip:9200 --pipeline=benchmark-only

You didn't specify the challenge; the eventdata tracks has several challenges and by not specifying a challenge it picked the default [elasticlogs-1bn-load](https://github.com/elastic/rally-eventdata-track/blob/e23b994e69b7b3ff8b0d386aa3b9a0a37f3e597d/eventdata/challenges/elasticlogs-1bn-load.json#L6-L8).

You should specify the `bulk-update` challenge if you want to take the blog article path (see how it's invoked [here](https://gist.github.com/dliappis/54a9eedd5a272cf13b49ecaa85f87c7f#file-configure_rally-sh-L87-L96)) or the `index-and-query-logs-fixed-daily-volume` if you want to use the other option I talked about [earlier](https://discuss.elastic.co/t/io-disc-tear-down-for-elastic-search/248013/2). In any case, please take a moment to go through the [available challenges docs](https://github.com/elastic/rally-eventdata-track#available-challenges) of the eventdata track.

You can also like all challenges in the track using e.g. `esrally info --track-repo=eventdata --track=eventdata`.

---

_[View the full topic](https://discuss.elastic.co/t/io-disc-tear-down-for-elastic-search/248013)._