ElasticSearch 因為磁盤空間不夠引起的數據插入錯誤。（message [ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]]） - 碼上歡樂

相關內容簡體繁體

ElasticSearch 因為磁盤空間不夠引起的數據插入錯誤。（message [ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]]）

本文轉載自查看原文 2018-05-25 14:42 6327 Elasticsearch/ 技術點滴

ES升級到624測試從Kettle插入數據的時候，經常提示如下錯誤

message [ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]]

可以理解就是索引是只讀模式，所以填入數據失敗。因為默認沒改過路徑，實際存儲應該在ES目錄下面。去看ES的啟動盤，發現基本已經滿了。可能確實因為存儲空間的原因。

參照這篇文檔，

https://www.cnblogs.com/huane/p/6093818.html

找到es的配置文件 elasticsearch.yml，把存儲數據的路徑改為其它空間比較大的盤符。

找到path.data路徑，取消掉注釋，並且指向新的可用空間較大的盤符。重新啟動ES，再插入數據，問題解決。

免責聲明！

本站轉載的文章為個人學習借鑒使用，本站對版權不負任何法律責任。如果侵犯了您的隱私權益，請聯系本站郵箱yoyou2525@163.com刪除。

猜您在找 Elasticserach 同步索引報錯：ElasticSearch ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)] 解決：ElasticSearch ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; ElasticSearch（十八）：解決org.elasticsearch.cluster.block.ClusterBlockException: blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; [ClusterBlockException[blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];]] ElasticSearch6 報錯blocked by: [FORBIDDEN/12/index read-only / allow delete (api)]; ElasticSearch、Logstash管理和監控——blocked by: [FORBIDDEN/12/index read-only / allow delete (api)] ELK elasticsearch 因磁盤爆滿導致無法 FORBIDDEN/12/index read-only / allow delete (api) ElasticSearch6 報錯FORBIDDEN/12/index read-only / allow delete (api) kibana報[FORBIDDEN/12/index read-only / allow delete (api)]錯誤 es報錯org.frameworkset.elasticsearch.ElasticSearchException: {"error":{"root_cause":[{"type":"cluster_block_exception","reason":"blocked by: [FORBIDDEN/12/index read-only / allow delete (api)];"}],

粵ICP備18138465號 © 2018-2025 CODEPRJ.COM