Issue

• Should I deploy my application bundles to the same container running the Fabric ensemble?

The Fuse Fabric Guide [1] provides the following recommendations:

Recommendations for an ensemble in production
To assure high availability of the Fabric registry in a production environment, it is recommended that you observe the following guidelines for a Fabric ensemble:

Deploy a minimum of five Fabric servers in production (if one server is taken down for maintenance, one other server can fail, and the Fabric registry will still be available).

Fabric servers should be deployed on separate host machines.

Each Fabric server should only have a Fabric registry agent deployed inside it. No other profiles should be deployed in it.

The size of the ensemble should be fixed at the outset, and not changed later (if you subsequently add or remove containers from the ensemble, the ZooKeeper IP ports would be re-assigned).

In particular, the recommendation for not deploying application bundles to the node running the ensemble server has been suggested to prevent cases where an application could cause the node to fail or become unreachable. Some conditions that could occur which can cause the node to fail or cause zookeeper to think the node is unreachable may include high CPU usage or OutOfMemory errors.