Go to the new link in the top toolbar called cluster. Enter the name of the servers to cluster together with the admin port used at the server. Note that the zookeeper port
should be the same at all nodes in a cluster.Adding nodes in the cluster, the current node is included by default
Next step is to verify that ports are opened between the nodes. Press the verify button. All lights must be green as in the figure bellow. During validation test connections are done between the nodes on zookeeper and database ports. These ports must be reachable for the cluster to work.
After a successful validation the cluster can be activated.
Check an active cluster
When the cluster is activated only the deactivate button is enabled and all lights should be green and all the database icon should have a green sync image. The figure bellow show a problem with synchronize the database at the 10.46.100.178 node. If this appear, restart that node.
When all nodes are up and running successful the view would look like the figure bellow The golden star image indicate the current master. The master has no database icon which is correct. The database sync icon indicate database replication. The database replication create one view over log files and jobs running in a clustered service.
Add a clustered service
In service maintenance there is a an option to mark the service to run in clustered mode. This has only effect when a cluster is active. Changes done for the service are synchronized to all nodes in the cluster. At runtime the different services behave differently. A Scheduler is active at all nodes but only one node submit the jobs to run, if the submitting node should go down another node take over the role as job submitter.