IO / Disc "tear down" for elastic search

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.

You should specify the bulk-update challenge if you want to take the blog article path (see how it's invoked here) or the index-and-query-logs-fixed-daily-volume if you want to use the other option I talked about earlier. In any case, please take a moment to go through the available challenges docs of the eventdata track.

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

1 Like