[sheepdog-users] bind option seems not to work
Ruoyu
liangry at ucweb.com
Fri Jul 25 12:26:39 CEST 2014
I guess, -b 192.168.2.45 means your sheep is about to listen on
192.168.2.45:7000 and if it is not specified, sheep is about to listen
on 0.0.0.0:7000.
To get what you want, you should use -y 192.168.2.45. It will tell
zookeeper that the node's address is 192.168.2.45
Valerio wrote:
Hi, my cluster has 3 nodes with 2 network cards (nic).
eth0 has an ip 192.168.2.0/24
eth1 has an ip 192.168.10.0/24
I stopped the cluster and changed sheep setting so to bind sheep to the
eth0 ip.
This way it shall not use eth1.
sheep -n /var/lib/sheepdog,/mnt/sheep/0 \
-b 192.168.2.45 \
-c zookeeper:192.168.2.45:2181,192.168.2.46:2181,192.168.2.47:2181
The same on the other 2 nodes setting the according ip.
I run sheep on the first node and you can already see what's wrong:
dog node list -a 192.168.2.45
Id Host:Port V-Nodes Zone
0 192.168.10.5:7000 128 84584640
it's using eth1 ip address instead of eth0!
Am I misunderstanding something or do I open a bug?
Thank you.
More information about the sheepdog-users
mailing list