# Event-data-track

**URL:** <https://discuss.elastic.co/t/event-data-track/174157>\
**Category:** Elasticsearch\
**Tags:** rally\
**Created:** [March 27, 2019, 3:08pm UTC](https://discuss.elastic.co/t/event-data-track/174157 "2019-03-27T15:08:33Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![asp](https://avatars.discourse-cdn.com/v4/letter/a/9fc348/32.png) [@asp](https://discuss.elastic.co/u/asp)\
**Post date:** [March 27, 2019, 3:08pm UTC](https://discuss.elastic.co/t/event-data-track/174157/1 "2019-03-27T15:08:33Z")

</div>

Hi,

the eventdata track on githup [https://github.com/elastic/rally-eventdata-track](https://github.com/elastic/rally-eventdata-track) has a lot of challenges.  
I am really interested in the following challenges :

- elasticlogs-querying
- combined-indexing-and-querying

Here are my questions:

- You mention you are running a 3 node cluster. The needed storage is the one per node or as sum? When I am testing a single node cluster, do I need to multiply storage by 3 or does it fit?
- is it quit easily doable to reduce the needed events from 1billion to lets say 250 or 500 mio? What do I need to change?

Thanks a lot,  
Andreas

---

<div class="post-metadata">

**Author:** ![danielmitterdorfer](https://sea2.discourse-cdn.com/elastic/user_avatar/discuss.elastic.co/danielmitterdorfer/32/110510_2.png) [@danielmitterdorfer](https://discuss.elastic.co/u/danielmitterdorfer)\
**Post date:** [March 28, 2019, 12:41pm UTC](https://discuss.elastic.co/t/event-data-track/174157/2 "2019-03-28T12:41:17Z")

</div>

Hi Andreas,

The eventdata track is a pretty sophisticated track and in general I think it pays off to study it in a bit more detail yourself along with our [track reference](https://esrally.readthedocs.io/en/stable/track.html) and our [tutorial how to create your own tracks](https://esrally.readthedocs.io/en/stable/adding_tracks.html).

> You mention you are running a 3 node cluster. The needed storage is the one per node or as sum? When I am testing a single node cluster, do I need to multiply storage by 3 or does it fit?

Ignoring replicas, index size is independent of the number of nodes.

> is it quit easily doable to reduce the needed events from 1billion to lets say 250 or 500 mio? What do I need to change?

From a Rally perspective this is definitely possible and we recommend to solve this via so-called track parameters that you can then pass as a command line parameter to Rally which in turn will apply it when loading the track. This track currently does not offer this as a track parameter but it would be definitely doable to add it and as an open source project we're always happy to receive pull requests. 🙂

Daniel

---

<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:** [April 25, 2019, 12:41pm UTC](https://discuss.elastic.co/t/event-data-track/174157/3 "2019-04-25T12:41:19Z")

</div>

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