How to revert metadata blocking?

ramazan · October 27, 2013, 7:32pm

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update API but
don't know how to revert it back.

I tried reverting it back using the fallowing command while the index in
close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_settings'
{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]
status: 403

}

Here is the gist:

gist.github.com

https://gist.github.com/rkarakaya/7186753

es_curls

//create an index
curl -XPUT 'http://127.0.0.1:9200/test1'
{
  "settings": {
    "index": {
      "number_of_shards": 1,
      "number_of_replicas": 0
    }
  }
}

This file has been truncated. show original

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Boaz_Leskes · October 28, 2013, 12:43pm

Hi,

I can't reproduce your error on master. My guess is that it is because the
curl syntax misses a -d parameter on the end. This causes no body to be sent

curl -XPUT "http://localhost:9200/test/_settings" -d'
{
"index": {
"blocks":{
"metadata":false
}
}
}'

I was wondering - why do you need to put a metadata block on a closed index?

On Sunday, October 27, 2013 8:32:59 PM UTC+1, rkar...@gmail.com wrote:

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update API
but don't know how to revert it back.

I tried reverting it back using the fallowing command while the index in
close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_settings'
{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]

status: 403

}

Here is the gist:
revert metadata blocking setting · GitHub

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

ramazan · October 31, 2013, 8:24pm

Hi,
Hi,

I'll retry this with the latest master code.
I wrote down curl commands just to explain the issue. I am not directly
using curl.

I was wondering - why do you need to put a metadata block on a closed
index?
I don't need actually
More than a year, I am working on an ES administration tool (Web based). I
encountered this issue while I am testing my gui.

On Monday, October 28, 2013 2:43:34 PM UTC+2, Boaz Leskes wrote:

Hi,

I can't reproduce your error on master. My guess is that it is because the
curl syntax misses a -d parameter on the end. This causes no body to be sent

curl -XPUT "http://localhost:9200/test/_settings" -d'
{
"index": {
"blocks":{
"metadata":false
}
}
}'

I was wondering - why do you need to put a metadata block on a closed
index?

On Sunday, October 27, 2013 8:32:59 PM UTC+1, rkar...@gmail.com wrote:

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update API
but don't know how to revert it back.

I tried reverting it back using the fallowing command while the index in
close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_settings'
{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]

status: 403

}

Here is the gist:
revert metadata blocking setting · GitHub

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Leonardo_Menezes · October 31, 2013, 8:58pm

maybe this is related:

github.com/elastic/elasticsearch

index.blocks.read_only prevents _status

opened 05:31PM - 29 Mar 13 UTC

closed 01:23PM - 23 Apr 15 UTC

devoncrouse

>bug v2.0.0-beta1 v1.6.0 :Distributed/Distributed

In trying to protect completed daily indices from future changes, we tried setti…ng 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?)

Leonardo Menezes
http://lmenezes.com

http://twitter.com/leonardomenezes

On Thu, Oct 31, 2013 at 9:24 PM, rkarakaya@gmail.com wrote:

Hi,
Hi,

I'll retry this with the latest master code.
I wrote down curl commands just to explain the issue. I am not directly
using curl.

I was wondering - why do you need to put a metadata block on a closed
index?
I don't need actually
More than a year, I am working on an ES administration tool (Web based). I
encountered this issue while I am testing my gui.

On Monday, October 28, 2013 2:43:34 PM UTC+2, Boaz Leskes wrote:

Hi,

I can't reproduce your error on master. My guess is that it is because
the curl syntax misses a -d parameter on the end. This causes no body to be
sent

curl -XPUT "http://localhost:9200/test/_**settings http://localhost:9200/test/_settings"
-d'
{
"index": {
"blocks":{
"metadata":false
}
}
}'

I was wondering - why do you need to put a metadata block on a closed
index?

On Sunday, October 27, 2013 8:32:59 PM UTC+1, rkar...@gmail.com wrote:

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update API
but don't know how to revert it back.

I tried reverting it back using the fallowing command while the index in
close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_**settings http://127.0.0.1:9200/test1/_settings'
{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[**blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]

status: 403

}

Here is the gist:
https://gist.github.com/**rkarakaya/7186753 https://gist.github.com/rkarakaya/7186753

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

ramazan · October 31, 2013, 9:23pm

yes. it seems similar.

My workaround is :
Don't allow user to change this setting

On Thursday, October 31, 2013 10:58:06 PM UTC+2, Leonardo Menezes wrote:

maybe this is related:
index.blocks.read_only prevents _status · Issue #2833 · elastic/elasticsearch · GitHub

Leonardo Menezes
http://lmenezes.com

http://twitter.com/leonardomenezes

On Thu, Oct 31, 2013 at 9:24 PM, <rkar...@gmail.com <javascript:>> wrote:

Hi,
Hi,

I'll retry this with the latest master code.
I wrote down curl commands just to explain the issue. I am not directly
using curl.

I was wondering - why do you need to put a metadata block on a closed
index?
I don't need actually
More than a year, I am working on an ES administration tool (Web based).
I encountered this issue while I am testing my gui.

On Monday, October 28, 2013 2:43:34 PM UTC+2, Boaz Leskes wrote:

Hi,

I can't reproduce your error on master. My guess is that it is because
the curl syntax misses a -d parameter on the end. This causes no body to be
sent

curl -XPUT "http://localhost:9200/test/_**settings http://localhost:9200/test/_settings"
-d'
{
"index": {
"blocks":{
"metadata":false
}
}
}'

I was wondering - why do you need to put a metadata block on a closed
index?

On Sunday, October 27, 2013 8:32:59 PM UTC+1, rkar...@gmail.com wrote:

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update API
but don't know how to revert it back.

I tried reverting it back using the fallowing command while the index
in close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_**settings http://127.0.0.1:9200/test1/_settings'

{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[**blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]

status: 403

}

Here is the gist:
https://gist.github.com/**rkarakaya/7186753 https://gist.github.com/rkarakaya/7186753

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearc...@googlegroups.com <javascript:>.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Leonardo_Menezes · October 31, 2013, 9:46pm

that's what I did... even though I did't really appreciate this kind of "no
turning back" operations. seems dangerous.

Leonardo Menezes
http://lmenezes.com

http://twitter.com/leonardomenezes

On Thu, Oct 31, 2013 at 10:23 PM, rkarakaya@gmail.com wrote:

yes. it seems similar.

My workaround is :
Don't allow user to change this setting

On Thursday, October 31, 2013 10:58:06 PM UTC+2, Leonardo Menezes wrote:

maybe this is related: https://github.com/**elasticsearch/elasticsearch/*
*issues/2833 https://github.com/elasticsearch/elasticsearch/issues/2833

Leonardo Menezes
http://lmenezes.com

http://twitter.com/leonardomenezes

On Thu, Oct 31, 2013 at 9:24 PM, rkar...@gmail.com wrote:

Hi,
Hi,

I'll retry this with the latest master code.
I wrote down curl commands just to explain the issue. I am not directly
using curl.

I was wondering - why do you need to put a metadata block on a closed
index?
I don't need actually
More than a year, I am working on an ES administration tool (Web based).
I encountered this issue while I am testing my gui.

On Monday, October 28, 2013 2:43:34 PM UTC+2, Boaz Leskes wrote:

Hi,

I can't reproduce your error on master. My guess is that it is because
the curl syntax misses a -d parameter on the end. This causes no body to be
sent

curl -XPUT "http://localhost:9200/test/_**s**ettings http://localhost:9200/test/_settings"
-d'
{
"index": {
"blocks":{
"metadata":false
}
}
}'

I was wondering - why do you need to put a metadata block on a closed
index?

On Sunday, October 27, 2013 8:32:59 PM UTC+1, rkar...@gmail.com wrote:

Hi,

I am facing an issue related to the metadata blocking setting.
I told ES to disable the metadata changes for an index using update
API but don't know how to revert it back.

I tried reverting it back using the fallowing command while the index
in close state.

curl -XPUT 'http://127.0.0.1:9200/test1/_****settings http://127.0.0.1:9200/test1/_settings'

{
"index": {
"blocks":{
"metadata":false
}
}

}

Bu it returned:

{

error: ClusterBlockException[blocked by: [FORBIDDEN/4/index
closed];[FORBIDDEN/8/index write (api)];]

status: 403

}

Here is the gist:
https://gist.github.com/**rkarak**aya/7186753 https://gist.github.com/rkarakaya/7186753

I hope someone help me.

NOTE: I am using a few day old master branch of ES.

Thanks.

--
You received this message because you are subscribed to the Google
Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send
an email to elasticsearc...@**googlegroups.com.

For more options, visit https://groups.google.com/**groups/opt_out https://groups.google.com/groups/opt_out
.

--
You received this message because you are subscribed to the Google Groups
"elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

--
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to elasticsearch+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

Topic		Replies	Views
Issue removing index with index.blocks.read_only set to true Elasticsearch	4	2325	July 6, 2017
It seems impossible to modify/delete an index after setting blocks.read_only=true Elasticsearch	1	417	July 6, 2017
Delete by query api - ClusterBlockException[blocked by: [FORBIDDEN/8/index write (api)];] status": 403 Elasticsearch	9	11917	July 5, 2017
Cluster_block_exception does not allow me to delete an index Elasticsearch	7	279	February 28, 2023
Value of index.blocks.write is auto changed to false Elasticsearch	3	1981	November 16, 2020

How to revert metadata blocking?

Related topics