Elasticsearch 6.2.3 崩溃经历

环境:jdk-10.0.1   + centos 7.14 

 

报错:

 

#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x00007f88722978d6, pid=23611, tid=24302
#
# JRE version: Java(TM) SE Runtime Environment (10.0.1+10) (build 10.0.1+10)
# Java VM: Java HotSpot(TM) 64-Bit Server VM (10.0.1+10, mixed mode, tiered, compressed oops, concurrent mark sweep gc, linux-amd64)
# Problematic frame:
# J 14628 c2 org.apache.lucene.util.MergedIterator.pullTop()V (135 bytes) @ 0x00007f88722978d6 [0x00007f88722972e0+0x00000000000005f6]
#
# No core dump will be written. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again
#
# If you would like to submit a bug report, please visit:
#   http://bugreport.java.com/bugreport/crash.jsp
#

---------------  S U M M A R Y ------------

Command Line: -Xms8g -Xmx8g -XX:+UseConcMarkSweepGC -XX:CMSInitiatingOccupancyFraction=75 -XX:+UseCMSInitiatingOccupancyOnly -XX:+AlwaysPreTouch -Xss1m -Djava.awt.headless=true -Dfile.encoding=UTF-8 -Djna.nosys=true -XX:-OmitStackTraceInFastThrow -Dio.netty.noUnsafe=true -Dio.netty.noKeySetOptimization=true -Dio.netty.recycler.maxCapacityPerThread=0 -Dlog4j.shutdownHookEnabled=false -Dlog4j2.disable.jmx=true -Djava.io.tmpdir=/elasticsearch/elasticsearch-6.2.3/tmp -XX:+HeapDumpOnOutOfMemoryError -Xlog:gc*,gc+age=trace,safepoint:file=logs/gc.log:utctime,pid,tags:filecount=32,filesize=64m -Djava.locale.providers=COMPAT -Des.path.home=/elasticsearch/elasticsearch-6.2.3 -Des.path.conf=/elasticsearch/elasticsearch-6.2.3/config org.elasticsearch.bootstrap.Elasticsearch -d

Host: Virtual CPU 82d9ed4018dd, 6 cores, 15G, CentOS Linux release 7.4.1708 (Core) 
Time: Tue Apr 24 12:52:15 2018 UTC elapsed time: 1209 seconds (0d 0h 20m 9s)

 定位 原因:

J 14628 c2 org.apache.lucene.util.MergedIterator.pullTop()


搜索不出什么结果.

崩溃前 GC 不断的执行,日志,使用的数据量很少。查询很少。

最后忽然有灵感,会不会jdk 版本太高了。换 jdk8.

果然 解决了问题

 

posted @ 2018-04-25 20:27  小湖海  阅读(1648)  评论(0编辑  收藏  举报