Interset's default documentation may cause a problem if you perform an installation with firewall enabled and on a dedicated network segment (in computer room) that has no outside connection with the exception of a mirror.
In this case network configuration may look like:
For /etc/sysconfig/network-scripts/ifcfg-eth0 file:
DEVICE=eth0
HWADDR=00:50:56:9E:77:7B
TYPE=Ethernet
UUID=8240d96c-4718-44b7-a81f-c968084932a7
ONBOOT=yes
NM_CONTROLLED=yes
BOOTPROTO=dhcp
DHCP_HOSTNAME=clientnode1
PEERDNS=no
For /etc/hosts file:
127.0.0.1 localhost localhost.localdomain localhost4 localhost4.localdomain4
::1 localhost localhost.localdomain localhost6 localhost6.localdomain6
172.17.97.75 mirror mirror.interset.com
172.17.97.63 datanode1 datanode1.interset.com
172.17.97.44 clientnode1 clientnode1.interset.com
172.17.97.64 endpointnode1 endpointnode1.interset.com
For /etc/resolv.conf file:
#; generated by /sbin/dhclient-script
#search interset.com
#nameserver 172.17.97.250
#nameserver 10.10.10.7
This will prevent hostname resolution for cassandra.yaml parameters like:
seeds: endpoint.interset.com
rpc_interface: eth0
listen_interface: eth0
However, if the aforementioned parameters are configured as:
seeds: "<IP1>,<IP2>"
rpc_address: <HOST_IP>
listen_address: <HOST_IP>
... then it will not cause any problems and on the other hand will work for any scenarios that you may choose.
Comments