-
Notifications
You must be signed in to change notification settings - Fork 25.8k
index.blocks.read_only prevents _status #2833
Copy link
Copy link
Closed
Labels
:Distributed/DistributedA catch all label for anything in the Distributed Area. Please avoid if you can.A catch all label for anything in the Distributed Area. Please avoid if you can.>bugv1.6.0v2.0.0-beta1
Description
In trying to protect completed daily indices from future changes, we tried setting index.blocks.read_only : true, but found that we were then unable to query _status, and head plugin could no longer display shard information. I think this best illustrates the behavior we're seeing, but not expecting:
curl -XGET 'http://localhost:9200/messages_20130301/_status'
{"error":"ClusterBlockException[blocked by: [FORBIDDEN/5/index read-only (api)];]","status":403}
Also, as an aside: what's the difference between index.blocks.read_only : true and index.blocks.write : true (which lets me query status and prevents delete?)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
:Distributed/DistributedA catch all label for anything in the Distributed Area. Please avoid if you can.A catch all label for anything in the Distributed Area. Please avoid if you can.>bugv1.6.0v2.0.0-beta1
Type
Fields
Give feedbackNo fields configured for issues without a type.