Skip to content
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

Closed
clintongormley opened this issue Feb 16, 2010 · 4 comments
Closed

flush_index returns both success and failure #20

clintongormley opened this issue Feb 16, 2010 · 4 comments

Comments

@clintongormley
Copy link
Contributor

while running the default server, just started with

./bin/elasticsearch -f

I create an index, then flush it, and it returns:

'{
   "ok" : true,
   "_shards" : {
      "failed" : 5,
      "successful" : 5,
      "total" : 10
   }
}
'

Why do 5 fail?

@kimchy
Copy link
Member

kimchy commented Feb 16, 2010

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.

@clintongormley
Copy link
Contributor Author

Thanks for the explanation

@kimchy
Copy link
Member

kimchy commented Feb 18, 2010

Closing this. Later on, I will add explicit explanation in the response as to why each shard failed...

@kimchy
Copy link
Member

kimchy commented Feb 24, 2010

Just an update, responses now return failure reasons which will make things a bit more usable.

dadoonet added a commit that referenced this issue Jun 5, 2015
We want to be able to release versions in a faster way then we do by now.

Closes #20.
dadoonet added a commit that referenced this issue Jun 5, 2015
dadoonet added a commit that referenced this issue Jun 5, 2015
Closes #20.

Thanks to @goncha!
(cherry picked from commit 333f850)
dadoonet added a commit that referenced this issue Jun 9, 2015
dadoonet added a commit that referenced this issue Jun 9, 2015
henningandersen pushed a commit to henningandersen/elasticsearch that referenced this issue Jun 4, 2020
* 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.
cbuescher pushed a commit to cbuescher/elasticsearch that referenced this issue Oct 2, 2023
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
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants