大网数据广告活动
服务器运维问答

Cloudera SCM Agent can't heartbeat but port is contactable

· 52CE 我爱测

I'm trying to add nodes to a Cloudera cluster. When the agent starts I get a python stacktrace saying it can't heartbeat to master-host:7182, however I can connect to that port just fine. The stacktrace is from Python and ends sa…

问题原文

原帖链接 · shearn89 · CC BY-SA 3.0

I'm trying to add nodes to a Cloudera cluster. When the agent starts I get a python stacktrace saying it can't heartbeat to master-host:7182, however I can connect to that port just fine.

The stacktrace is from Python and ends saying the connection timed out.

nc -z 1 -w master-host 7182 returns "connection successful"

Firewalls are off, SELinux is in Permissive.

Each box has 2 IPs, one in the 4 space and one in the 8 space. The DNS resolves the 8 address and the hosts file resolves the 4 address.

EDIT: To add some more info, based on this post:

  • OS Versions are the same, agent/manager versions are the same
  • I can connect from the CM host to the 4 address, port 9000. The 4 address is the one that shows up in the Host page on Cloudera Manager
  • The large ping command fails on the 4 address: ping -c 3 -s 1800 4-address, MTU for this interface is set to 9000.
  • The large ping command passes on the 8 address, MTU is set to 1500.

已采纳解答

原帖链接 · shearn89 · CC BY-SA 3.0

Turns out the MTU appeared to be the issue - the infrastructure we're using wasn't supporting jumbo frames end-to-end (in this case, Cisco c240m4s with fibre interconnects needed the QoS settings updating via UCS).

摘自公开归档,保留原文语言,版式经整理,外部媒体与邮箱地址已移除。

资料来源与适用范围

资料来源
Server Fault
适用范围
以原帖系统、软件版本与发布日期为准(2016-03-22)
内容语言
中文;命令、路径和错误标识保留技术原文
本地收录日期
2026-11-15
授权说明
CC BY-SA 3.0

正文与所需资源由本站本地存储。查看来源及更新记录 ↗

请按适用版本和实际日志确认原因;本站没有对每一种系统或设备逐项执行文中的操作。