Hi! Saw that ELK 7.0 was available and upgraded my lab. After that I got these errors from logstash: Apr 11 13:01:38 linuxmgmt.j.local logstash[29896]: [2019-04-11T13:01:38,243][INFO ][logstash.outputs.elasticsearch] retrying failed action with response code: 403 ({"type"=>"cluster_block_exception…

This block is applied when running out of disk space indeed, and that's the only circumstances under which it is automatically applied. There will be messages in the server log giving details of how Elasticsearch arrived at this decision. Look for messages from a logger called DiskThresholdMonitor. …

Index read-only after upgrading to 7.0

Elastic Stack Elasticsearch

epacke (Patrik Jonsson) April 21, 2019, 12:14pm 3

Thanks David. I deleted a few days of data and everything started to work again.

Kind regards,
Patrik

1 Like

Topic		Replies	Views
"cluster_block_exception", "reason"=>"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}) Elasticsearch	5	53347	January 28, 2019
Elasticsearch Error {type:cluster_block_exception,reason:"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];} Elasticsearch	5	4476	November 21, 2019
Blocked by: [FORBIDDEN/12/index read-only / allow delete (api) Elasticsearch	5	5547	March 22, 2018
Document Index error:- index [....] blocked by: [FORBIDDEN/12/index read-only / allow delete (api)] Elasticsearch	5	592	February 18, 2020
[FORBIDDEN/12/index read-only Elasticsearch ilm-index-lifecycle-management	8	2238	April 9, 2019

Index read-only after upgrading to 7.0

Related topics