ClusterBlockException after upgrade 1.7 to 2.1


(Grégory) #1

Hello,

I upgraded my cluster from 1.7 to 2.1. Everything was green with the migration plugin.
Some of my indices where set as read only.
After the upgrade ALL my indices are not readable. I got a ClusterBlockException when a do a basic _search request. Indices are OPEN.

Here is the config of the cluster and a index:

The only solution i have is to re-index everything but it's HUGE!

Any idea to solve this ?


(Magnus Bäck) #2

Please post the full error message. Is the cluster still green?


(Grégory) #3

I retrieved the full message

{"error":{"root_cause":[{"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/5/index read (api)];"}],"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/5/index read (api)];"},"status":403}


(Magnus Bäck) #4

Looks like the index is read only. You don't have index.blocks.read_only set to true in the index settings have you?


(Grégory) #5

I posted my index cluster settings and in both there is :

"blocks": {
"read_only": "false"
}

But, even if the index is considered "read-only", it should be readable. In my case, i can't query (_search) on it


(system) #6