Fuse Fabric zookeeper bind address

[rafaelcba]

Is possible to set a fixed network address for zookeeper in Fuse Fabric?

I noticed that every time the host IP address changes the Fabric bind address changes and all the Fabric (root and child container) become unstable. Some times I have to delete my containers and create again or even create a new clean fabric.

I used to change the zookeeper url manually:

config:edit io.fabric8.zookeeper
config:propset zookeeper.url <hostname>:2181
config:update

Is that the default behavior? How it works? How about host with multiple network interfaces (a common case in production environments)?

It appears zookeeper listen for IP changes.

I would appreciate any explanation or reference to better understand the Fabric's network behavior.

kind regards.

[pcootey]

This is default behavior.

https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html/Fabric_Guide/files/ESBRuntimeFabricCreate.html

"The IP address and hostname associated with the Fabric Servers in the Fabric ensemble are of critical importance to the fabric. Because these IP addresses and hostnames are used for configuration and service discovery (through the Zookeeper registry), they must not change during the lifetime of the fabric."

[rafaelcba]

Hi pcootey!

Thanks for you reply.

I saw that note in the Fuse Docs. But It does not say how to (or if is possible) deal with IP changes in a Fabric environment.

[davsclaus]

Yeah I think if an IP needs to be changed, you can use fabric:ensemble-leave to leave and then do the IP change, and then add/ join afterwards.

[mike.hepburn]

i've found editing instances/instance.properties (including all container instance.properties) with the new hostname/ip.address as well as correctly setting hostname (in either linux or windows) will do the trick ...

fabric:ensemble-leave is only available if/when zookeeper starts ! so, if you reconfigure networking, or copy-n-past fuse - you may have better luck leaving the ensemble *first*

HTH

[rafaelcba]

I think the best way to avoid IP addr changes in a multi-homed host (or in a local env) is creating the fabric with manualip resolver:

JBossFuse:karaf@root> fabric:create --resolver manualip --manual-ip CustomIPAddress
  --zookeeper-password admin --wait-for-provisioning

By default Fuse creates the fabric with the localhostname resolver, which can change dynamically.

See https://access.redhat.com/documentation/en-US/Red_Hat_JBoss_Fuse/6.1/html-single/Configuring_and_Running_Red_Hat_JBoss_F… for more details.