elasticsearch报错 all shards failed修复

启动后查看日志报错all shards failed
1.查看健康状态

[root@iZbp1bzugfiorbfrhd333aZ ~]# curl -XGET 'http://172.16.163.226:9200/_cluster/health?pretty=true'
{"cluster_name" : "es-1","status" : "yellow",    ####未修复前为red"timed_out" : false,"number_of_nodes" : 1,"number_of_data_nodes" : 1,"active_primary_shards" : 2041,"active_shards" : 2041,"relocating_shards" : 0,"initializing_shards" : 0,"unassigned_shards" : 5,"delayed_unassigned_shards" : 0,"number_of_pending_tasks" : 0,"number_of_in_flight_fetch" : 0,"task_max_waiting_in_queue_millis" : 0,"active_shards_percent_as_number" : 99.75562072336265  ######未修复前为百分之40左右
}

2.查看损坏索引

curl -XGET 'http://172.16.163.226:9200/_cat/indices?v&pretty'

基本都是red和yellow为主
3.进行第一次修复：

curl -H "Content-Type: application/json" -XPUT 'http://172.16.163.226:9200/_all/_settings' -d '
{"index" : {"number_of_replicas" : 0}
}'

基本都为green了
**4.第二次修复，**发现还有一些损坏无法修复的直接删除类似如下

curl -XDELETE  "http://127.0.0.1:9200/test*

在进行日志查看的是否都为green了，启动

5.kibana报错Request Timeout after 30000ms启动报错

查看报错内存不足引起，2g改成4g，正常启动恢复

vi /home/es/elasticsearch-6.8.4/config/jvm.options# Xms represents the initial size of total heap space
# Xmx represents the maximum size of total heap space-Xms4g
-Xmx4g

5.总结
估计是内存不足导致索引损坏引起的本次无法启动

引用内容：
https://blog.csdn.net/qq_40907977/article/details/104499178
https://www.cnblogs.com/likecs/p/14983881.html
https://www.cnblogs.com/gooooodmorning/p/13611825.html
https://www.cnblogs.com/zhangb8042/articles/11346085.html

elasticsearch报错 all shards failed修复相关推荐

【Kibana】es 报错 all shards failed: [search_phase_execution_exception] all shards failed
1.背景访问kibana报错,all shards failed {"message":"all shards failed: [search_phase_execut ...
Linux报错superblock read failed修复
xfs文件系统是不支持减容的,刚好碰到,这里用试验还远下重现故障恢复过程这里把var使用lvreduce进行减容把31变成20g ,问了是否选了Y ,这边y敲下去,就凉了! [root@YYYJUN ...
ElasticSearch报错：FORBIDDEN/12/index read-only / allow delete (api)无法写入
背景一个两年前的读书笔记项目,在本地开发环境启动后,搜索服务的后端日志 ElasticSearch 报错:FORBIDDEN/12/index read-only / allow delete (a ...
解决只读模式U盘保护格式化或者dd写报错：ERROR: failed to open ‘/dev/sdb‘ in read-write mode: Read-only file system.
解决只读模式U盘保护格式化或者dd写报错:ERROR: failed to open '/dev/sdb' in read-write mode: Read-only file system. 或者: ...
gitlab报错 fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200解决方案
gitlab报错 "fatal: index-pack failed error: RPC failed; result=18, HTTP code = 200",如下图这个问题 ...
centos6.5报错:checking filesystems failed问题处理
centos系统重启报错:checking filesystems failed checking filesystems /dev/mapper/vg_0-root: 搜了下可能是文件系统损坏根据 ...
cordova编译报错：Execution failed for task ':processDebugResources'
cordova编译报错:Execution failed for task ':processDebugResources' 引发这个错误的最扩祸首就是一个中文命名的文件,不知道什么时候加入的,我写了 ...
elasticsearch报错expected ＜block end＞, but found BlockMappingStart解决方法
elasticsearch报错expected , but found BlockMappingStart解决方法参考文章: (1)elasticsearch报错expected , but fou ...
git配置报错fatal: Authentication failed for ‘‘问题解决
git配置报错fatal: Authentication failed for ''问题解决参考文章: (1)git配置报错fatal: Authentication failed for ''问题 ...

elasticsearch报错 all shards failed修复

elasticsearch报错 all shards failed修复相关推荐

最新文章

热门文章