行动是治愈恐惧的良药,而犹豫、拖延将不断滋养恐惧。

elasticsearch 源码启动异常: vmop

Elasticsearch | 作者 sun_changlong | 发布于2019年04月24日 | 阅读数:5718

[es@localhost elasticsearch]$ ./bin/elasticsearch
warning: Falling back to java on path. This behavior is deprecated. Specify JAVA_HOME
[b]vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count[/b]
0.234: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.255: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.279: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.332: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.525: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.559: Deoptimize [ 10 0 0 ] [ 0 0 0 0 0 ] 0
^C vmop [threads: total initially_running wait_to_block] [time: spin block sync cleanup vmop] page_trap_count
0.933: Exit [ 11 0 1 ] [ 0 0 0 0 0 ] 0
上述启动时报的异常;log中出现gc文件,文件详情如下:
  1 OpenJDK 64-Bit Server VM (25.201-b09) for linux-amd64 JRE (1.8.0_201-b09), built on Mar 11 2019 17:57:19 by "mockbuild" with gcc 4.4.7 20120313 (Red Hat 4.4.7-23)
2 Memory: 4k page, physical 7953900k(3062428k free), swap 8388600k(8388600k free)
3 CommandLine flags: -XX:+AlwaysPreTouch -XX:CMSInitiatingOccupancyFraction=75 -XX:ErrorFile=logs/hs_err_pid%p.log -XX:GCLogFileSize=67108864 -XX:+HeapDumpOnOutOfMemoryErr or -XX:HeapDumpPath=data -XX:InitialHeapSize=2147483648 -XX:MaxHeapSize=2147483648 -XX:MaxNewSize=697933824 -XX:MaxTenuringThreshold=6 -XX:NewSize=697933824 -XX:NumberOf GCLogFiles=32 -XX:OldPLABSize=16 -XX:OldSize=1395867648 -XX:-OmitStackTraceInFastThrow -XX:+PrintGC -XX:+PrintGCApplicationStoppedTime -XX:+PrintGCDateStamps -XX:+PrintG CDetails -XX:+PrintGCTimeStamps -XX:+PrintSafepointStatistics -XX:PrintSafepointStatisticsCount=1 -XX:+PrintTenuringDistribution -XX:ThreadStackSize=1024 -XX:+UseCMSInit iatingOccupancyOnly -XX:+UseCompressedClassPointers -XX:+UseCompressedOops -XX:+UseConcMarkSweepGC -XX:+UseGCLogFileRotation -XX:+UseParNewGC
4 2019-04-24T14:11:03.736+0800: 0.208: Total time for which application threads were stopped: 0.0000884 seconds, Stopping threads took: 0.0000112 seconds
5 2019-04-24T14:11:03.764+0800: 0.237: Total time for which application threads were stopped: 0.0000863 seconds, Stopping threads took: 0.0000122 seconds
6 2019-04-24T14:11:03.789+0800: 0.261: Total time for which application threads were stopped: 0.0000807 seconds, Stopping threads took: 0.0000113 seconds
7 2019-04-24T14:11:03.843+0800: 0.315: Total time for which application threads were stopped: 0.0001031 seconds, Stopping threads took: 0.0000121 seconds
8 2019-04-24T14:11:04.033+0800: 0.506: Total time for which application threads were stopped: 0.0001335 seconds, Stopping threads took: 0.0000137 seconds
9 2019-04-24T14:11:04.066+0800: 0.538: Total time for which application threads were stopped: 0.0001334 seconds, Stopping threads took: 0.0000121 seconds
10 2019-04-24T14:11:04.499+0800: 0.971: Total time for which application threads were stopped: 0.0002045 seconds, Stopping threads took: 0.0000127 seconds
11 2019-04-24T14:11:04.618+0800: 1.091: Total time for which application threads were stopped: 0.0002021 seconds, Stopping threads took: 0.0000140 seconds
12 2019-04-24T14:11:04.751+0800: 1.224: Total time for which application threads were stopped: 0.0002220 seconds, Stopping threads took: 0.0000154 seconds
13 2019-04-24T14:11:04.993+0800: 1.465: Total time for which application threads were stopped: 0.0002022 seconds, Stopping threads took: 0.0000133 seconds
14 Heap
15 par new generation total 613440K, used 120046K [0x0000000080000000, 0x00000000a9990000, 0x00000000a9990000)
16 eden space 545344K, 22% used [0x0000000080000000, 0x000000008753b990, 0x00000000a1490000)
17 from space 68096K, 0% used [0x00000000a1490000, 0x00000000a1490000, 0x00000000a5710000)
18 to space 68096K, 0% used [0x00000000a5710000, 0x00000000a5710000, 0x00000000a9990000)
19 concurrent mark-sweep generation total 1415616K, used 0K [0x00000000a9990000, 0x0000000100000000, 0x0000000100000000)
20 Metaspace used 16380K, capacity 16840K, committed 16896K, reserved 1064960K
21 class space used 1866K, capacity 2034K, committed 2048K, reserved 1048576K


 
当前内存使用请款如下:
[es@localhost elasticsearch]$ free -m
total used free shared buffers cached
Mem: 7767 4774 2992 0 46 2957
-/+ buffers/cache: 1770 5996
Swap: 8191 0 8191


请问这种 gc 问题,我该如何查找异常点? 以及如何结束这种异常报错?
还请了解的大佬留下宝贵的建议和指点
 
已邀请:

xiaoke - http://blog.51cto.com/kexiaoke

赞同来自:

你启动的时候JVM设置的多少?

zqc0512 - andy zhou

赞同来自:

你配置环境变量看下。
1.你配置环境变量看下。
2.(Red Hat 4.4.7-23) 这是撒版本?
3.ES对应的是撒版本?
4.数据量有多大?

要回复问题请先登录注册