I was creating a custom track and accidentally specified invalid index settings. My problem is that esrally happily continued on and didn't produce any output that alerted me to this fact and I was just confused that my index was getting created improperly.
I eventually found a log line that produced a WARNING, but I was wondering if there was an option/flag so that esrally would create an error when a step fails.
2019-12-27 01:16:18,878 -not-actor-/PID:84505 elasticsearch WARNING PUT http://localhost:9200/bad-track [status:400 request:0.016s]
Is it expected that the create-index operation doesn't fail on error?
@dliappis following up, is there a way for a track to specify an on-error behavior per operation? Or just for the whole track? For example, like the reasoning you linked to, an error for indexing is "data" but an error for index creation invalidates the track.
Apache, Apache Lucene, Apache Hadoop, Hadoop, HDFS and the yellow elephant
logo are trademarks of the
Apache Software Foundation
in the United States and/or other countries.