-
Notifications
You must be signed in to change notification settings - Fork 24.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
flush_index returns both success and failure #20
Comments
Its because, by default, an index is created with 5 shards, each with one replica. When you start a single node, only 5 shards are allocated on that node, when you start another one, the other 5 replicas will be allocated. The failed ones refer to the 5 shards that have not been started yet. |
Thanks for the explanation |
Closing this. Later on, I will add explicit explanation in the response as to why each shard failed... |
Just an update, responses now return failure reasons which will make things a bit more usable. |
We want to be able to release versions in a faster way then we do by now. Closes #20.
* Added challenge for large shard sizing and improved indicessstats * Increased indexing concurrency * Corrected iteration count * Corrected large shard benchmark description * Corrected large shard benchmark description * Added warning about disk space requirements for large shard sizing challenge. * Fixed minor spelling mistake.
With this commit we add a new mode to night-rally: adhoc. It allows to run our benchmark suite for arbitrary commit hashes and publish the results. night-rally now also records the results of release-benchmarks in the ES metrics store. Closes elastic#20
while running the default server, just started with
I create an index, then flush it, and it returns:
Why do 5 fail?
The text was updated successfully, but these errors were encountered: