Migration Problem 6.0

After trying to migrate from 5.3 (via 5.6) to 6.0 i have to face sharding errors.
My Indecies seemed to be looked and i can not revert from this status.

My setting looks like this and read_only is set to false and write as well...
{
".kibana-6": {
"settings": {
"index": {
"number_of_shards": "1",
"blocks": {
"read_only_allow_delete": "true",
"read_only": "false",
** "write": "false"**
},
"provided_name": ".kibana-6",
"mapper": {
"dynamic": "false"
},
"creation_date": "1511359816799",
"number_of_replicas": "1",
"uuid": "wOw0PHNGSZuWNIB-a8Yhjw",
"version": {
"created": "5060099",
"upgraded": "6000099"
}
}
}
}
}

Trying to set write to true leads me to this error message

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

This is the same error i see when I'm at the discovermode on certain indicies

Error: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];: [cluster_block_exception] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];
at http://localhost:5601/bundles/kibana.bundle.js?v=16070:27:28530
at processQueue (http://localhost:5601/bundles/commons.bundle.js?v=16070:39:9912)
at http://localhost:5601/bundles/commons.bundle.js?v=16070:39:10805
at Scope.$digest (http://localhost:5601/bundles/commons.bundle.js?v=16070:39:21741)
at Scope.$apply (http://localhost:5601/bundles/commons.bundle.js?v=16070:39:24520)
at done (http://localhost:5601/bundles/commons.bundle.js?v=16070:38:9495)
at completeRequest (http://localhost:5601/bundles/commons.bundle.js?v=16070:38:13952)
at XMLHttpRequest.xhr.onload (http://localhost:5601/bundles/commons.bundle.js?v=16070:38:14690)

I also see at other indecies sharding errors
Courier Fetch: 1 of 5 shards failed.

Could anyone help me on this
?

TRY Using below command :

PUT your_index/_settings
{
"index": {
"blocks": {
"read_only_allow_delete": "false"
}
}
}

2 Likes

Thank you, sujeetKumar!

Thank you very much for your post.
That was very helpful

I found that problem has many people but no one is talking about solution
Can anyone tell what can be the cause when .kibana index is going to read-only state?
I know that It happens when the disk is close to full out, but in my case the partition have had a lot of free space.
Any suggestions?

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.