Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Various cleanups for Elasticsearch test #51
This change makes four changes:
In order to actually determine the root cause of issues, more verbose logging is needed. This defaults to more verbose logging for Elasticsearch and adds the ability to change it from Jepsen in the future (instead of manually by hand).
Without this, Jepsen deletes all traces of itself after running, which makes debugging much more difficult (no logs and no data left).
An optional change, but I figured I would make this change anyway.
This is a key part of testing Elasticsearch, and clients should always do this when creating indices.
Note that I was able to reproduce the failures in elastic/elasticsearch#10426 (about half of the time) without these changes, however after the change which waits for green after index creation, I am no longer able to reproduce data loss with the