Cloudera Manager -服务监控崩溃

Question

去年，我一直在使用Cloudera管理器来运行20+节点。最近，我开始在服务监视器角色中看到堆内存大小问题。我从3增加到4，然后从4增加到5，然后从5增加到6 GB。但是，有时我还是会让服务监视器崩溃并重新启动。在这段时间里，整个仪表板看起来都很糟糕。我需要在这里做些什么来解决这个问题？

日志是

2021-04-26 16:10:34,938 WARN com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 20583ms: GC pool 'G1 Young Generation' had collection(s): count=2 time=182ms, GC pool 'G1 Old Generation' had collection(s): count=1 time=20877ms 2021-04-26 16:11:34,862 WARN com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 19870ms: GC pool 'G1 Young Generation' had collection(s): count=2 time=131ms, GC pool 'G1 Old Generation' had collection(s): count=1 time=20228ms 2021-04-26 16:12:35,132 WARN com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 20427ms: GC pool 'G1 Young Generation' had collection(s): count=3 time=149ms, GC pool 'G1 Old Generation' had collection(s): count=1 time=20733ms 2021-04-26 16:13:36,415 WARN com.cloudera.enterprise.debug.JvmPauseMonitor: Detected pause in JVM or host machine (e.g. a stop the world GC, or JVM not scheduled): paused approximately 19008ms: GC pool 'G1 Young Generation' had collection(s): count=1 time=104ms, GC pool 'G1 Old Generation' had collection(s): count=1 time=19381ms

你能帮我弄一下这个吗？

Answer 1

根据集群中的主机数量、服务类型和当前被监控的实体数量，服务监视器可能会占用更高的内存。基于上述因素，给出了一个明确的here指南。

您可能需要根据集群的使用情况不断增加堆大小。在同一页面上有一些调优技巧，例如使用G1GC。

众所周知，HBase、Solr、Kafka和Kudu会生成大量实体，并增加服务监视器堆的需求。

如果您订阅了Cloudera支持，请提交案例以获得专家的官方支持。