 |
Philip Zeyliger |
at May 23, 2013 at 6:09 pm
|
⇧ | 
| |
Hi geehoot64,
By default, CM uses the hostname of the machine. Roughly like so:
$python -c 'import socket; print socket.getfqdn(),
socket.gethostbyname(socket.getfqdn())'
cairn 1.2.3.4
You can override that by editing /etc/cloudera-scm-agent/config.ini
(listening_hostname) and/or adding command line flags to
/etc/default/cloudera-scm-agent (see
https://groups.google.com/a/cloudera.org/forum/?fromgroups#!topic/scm-users/eyaN5p5cl8o).The distinction between "host-id" and "hostname" is subtle. If you were to
want to rename a host from A to B, but you wanted to keep everything the
same, you can maintain host-id the same while changing hostname.
-- Philip
On Thu, May 23, 2013 at 5:20 AM, wrote:
What is the criteria by which the cloudera-scm-agent determines which host
name/IP address to use? And on the server side, does it listen on all NIC
ports for an scm-agent heartbeat? I'm trying to change the network used by
the cloudera (the hosts are all dual homed) and I keep getting the agent
being reported on the old address on the host page of the manager GUI.
There is something stale somewhere that I can't clear by deleting the
offending host, restarting agents and servers, etc. How do you completely
flush out old information about a host?
