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

Closed indices should not cause block failures on some APIs what executing against _all indices #1010

Closed
clintongormley opened this issue Jun 9, 2011 · 1 comment

Comments

@clintongormley
Copy link

curl -XPUT 'http://127.0.0.1:9200/foo/?pretty=1' 
curl -XPUT 'http://127.0.0.1:9200/baz/?pretty=1' 
curl -XPOST 'http://127.0.0.1:9200/foo/bar?pretty=1'  -d '
{
   "text" : "foo"
}
'
curl -XPOST 'http://127.0.0.1:9200/baz/bar?pretty=1'  -d '
{
   "text" : "foo"
}
'

curl -XPOST 'http://127.0.0.1:9200/foo/_close?pretty=1' 

# [Thu Jun  9 20:29:53 2011] Response:
# {
#    "ok" : true,
#    "acknowledged" : true
# }

curl -XGET 'http://127.0.0.1:9200/_all/_search?pretty=1' 

# [Thu Jun  9 20:30:04 2011] Response:
# {
#    "status" : 500,
#    "error" : "ClusterBlockException[blocked by: [4/index closed];
# >    ]"
# }
@mobz
Copy link

mobz commented Jun 24, 2011

This pretty much breaks casual browsing on elasticsearch-head when one or more indices are closed.

@kimchy kimchy closed this as completed in b275e6f Jul 10, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants