Cloudera 内存不足 Java Runtime Environment 无法继续

Question

我尝试将我的 public dns 实例连接到端口 7180 上的 cloudera

我在网络浏览器中收到 'Unable to connect' 消息。

我使用 EC2 AWS + RedHat7 + Cloudera 5

当我启动 Cloudera Server 时，我收到消息：

root@ip-100-10-10-10 sysconfig]#  service cloudera-scm-server start 
Starting cloudera-scm-server (via systemctl):              [  OK  ]

当我卷曲时我得到：

[root@ip-100-10-10-10 sysconfig]# curl -i -u ‘admin:admin’ http://localhost:7180/api/v1/tools/echo
curl: (7) Failed connect to localhost:7180; Connection refused

这是 cloudera 服务器的日志文件，命令为 sudo ls -l /var/log/cloudera-scm-server

[root@ip-172-31-45-90 sysconfig]# $sudo cat /var/log/cloudera-scm-server/cloudera-scm-server.out 
JAVA_HOME=/usr/java/jdk1.7.0_67-cloudera
Java HotSpot(TM) 64-Bit Server VM warning: INFO: os::commit_memory(0x0000000787295000, 155291648, 0) failed; error='Cannot allocate memory' (errno=12)
#
# There is insufficient memory for the Java Runtime Environment to continue.
# Native memory allocation (malloc) failed to allocate 155291648 bytes for committing reserved memory.
# An error report file with more information is saved as:
# /tmp/hs_err_pid2370.log

如何解决？

Answer 1

I use EC2 AWS ... I have chosen the basic one, the one for free

阅读Cloudera Manager installation guide

RAM - 4 GB is appropriate for most cases, and is required when using Oracle databases. 2 GB may be sufficient for non-Oracle deployments involving fewer than 100 hosts. However, if you want to run the Cloudera Manager Server on a machine with 2 GB of RAM, you must tune down its maximum heap size (by modifying -Xmx in /etc/default/cloudera-scm-server). Otherwise the kernel may kill the Server for consuming too much RAM

我会更进一步说这是推荐的免费 space，所以如果你计划 [=22=，我建议 6 或 8GB ] 所有服务。 t2.micro、t2.nano 或您拥有的任何实例类型都没有那么多内存。

Cloudera 内存不足 Java Runtime Environment 无法继续

Cloudera insufficient memory for the Java Runtime Environment to continue

java

memory

cloudera