使用netstat -lntp来看看有侦听在网络某端口的进程。当然,也可以使用 lsof。

kibana启动失败,es日志错误如下[求大佬解决]

匿名 | 发布于2019年10月30日 | 阅读数:108

2019-10-30T12:50:53.169+0800: 522619.650: Total time for which application threads were stopped: 0.0057632 seconds, Stopping threads took: 0.0001217 seconds
2019-10-30T12:55:46.105+0800: 522912.586: Total time for which application threads were stopped: 0.0005035 seconds, Stopping threads took: 0.0001200 seconds
2019-10-30T12:55:46.105+0800: 522912.587: Total time for which application threads were stopped: 0.0002962 seconds, Stopping threads took: 0.0000714 seconds
2019-10-30T12:55:48.325+0800: 522914.807: Total time for which application threads were stopped: 0.0006094 seconds, Stopping threads took: 0.0001544 seconds
2019-10-30T12:55:51.095+0800: 522917.576: Total time for which application threads were stopped: 0.0005133 seconds, Stopping threads took: 0.0001490 seconds
2019-10-30T12:55:51.095+0800: 522917.576: Total time for which application threads were stopped: 0.0002935 seconds, Stopping threads took: 0.0000592 seconds
2019-10-30T13:07:46.562+0800: 523633.043: Total time for which application threads were stopped: 0.0012233 seconds, Stopping threads took: 0.0002602 seconds
2019-10-30T13:07:46.562+0800: 523633.043: Total time for which application threads were stopped: 0.0001688 seconds, Stopping threads took: 0.0000397 seconds
2019-10-30T13:07:46.575+0800: 523633.056: Total time for which application threads were stopped: 0.0003112 seconds, Stopping threads took: 0.0000921 seconds
2019-10-30T13:07:46.575+0800: 523633.057: Total time for which application threads were stopped: 0.0001764 seconds, Stopping threads took: 0.0000505 seconds
2019-10-30T13:08:12.215+0800: 523658.697: Total time for which application threads were stopped: 0.0004861 seconds, Stopping threads took: 0.0000936 seconds
2019-10-30T13:08:12.215+0800: 523658.697: Total time for which application threads were stopped: 0.0002149 seconds, Stopping threads took: 0.0000313 seconds
2019-10-30T13:08:12.259+0800: 523658.741: Total time for which application threads were stopped: 0.0004114 seconds, Stopping threads took: 0.0000823 seconds
2019-10-30T13:08:14.260+0800: 523660.741: Total time for which application threads were stopped: 0.0005114 seconds, Stopping threads took: 0.0001426 seconds
2019-10-30T13:08:24.245+0800: 523670.726: Total time for which application threads were stopped: 0.0004005 seconds, Stopping threads took: 0.0000774 seconds
2019-10-30T13:30:37.926+0800: 525004.408: Total time for which application threads were stopped: 0.0006618 seconds, Stopping threads took: 0.0001498 seconds
2019-10-30T13:30:39.046+0800: 525005.527: Total time for which application threads were stopped: 0.0004312 seconds, Stopping threads took: 0.0001071 seconds
2019-10-30T13:30:39.070+0800: 525005.551: Total time for which application threads were stopped: 0.0003990 seconds, Stopping threads took: 0.0001017 seconds
2019-10-30T13:30:39.070+0800: 525005.551: Total time for which application threads were stopped: 0.0001565 seconds, Stopping threads took: 0.0000311 seconds
2019-10-30T13:30:39.132+0800: 525005.614: [GC (Allocation Failure) 2019-10-30T13:30:39.132+0800: 525005.614: [ParNew
Desired survivor size 17891328 bytes, new threshold 6 (max 6)
- age 1: 1024256 bytes, 1024256 total
- age 2: 788784 bytes, 1813040 total
- age 3: 717376 bytes, 2530416 total
- age 4: 534512 bytes, 3064928 total
- age 5: 355648 bytes, 3420576 total
- age 6: 140808 bytes, 3561384 total
: 288893K->5235K(314560K), 0.0087384 secs] 576219K->292562K(1013632K), 0.0089356 secs] [Times: user=0.06 sys=0.00, real=0.01 secs]
已邀请:

Marquezzzz

赞同来自:

从日志上分析,gc失败了,没有多余的空间给eden区,可能是kibana在es上做了吃内存的聚合操作。从配置上来看,总堆内存只有1g,新生代只有300m,配置偏低。


"Allocation Failure" means that no more space left in Eden to allocate object. So, it is normal cause of young GC.

要回复问题请先登录注册