Creating a Server Cluster

This section provides you with guidelines and procedures for adding horizontal scalability and high availability to your CloudBees Flow environment. Horizontal scalability and high availability are achieved by adding additional machines to a CloudBees Flow configuration to create a server cluster. A clustered configuration of CloudBees Flow servers also requires these software components:

  • Apache ZooKeeper, which is a centralized service for maintaining and synchronizing group services in a cluster.

  • A software or hardware load balancer for routing work to machines in the cluster.

These components typically need to be managed by your IT department.

This section includes the Creating a DevOps Insight Server Cluster section, which describes the overall steps for adding machines to create a DevOps Insight server cluster. Also included is information about cluster upgrades, cluster reconfigurations, and configuring a cluster.

Benefits from Clustering

A clustered CloudBees Flow configuration has the following benefits:

  1. Adds fault tolerance by rerouting jobs and API requests to running Flow servers.

  2. Increases the supported number of simultaneous jobs and API requests.

  3. Distributes API requests across multiple Flow servers.

  4. Expands capacity over time by adding additional Flow servers.

  5. Distributes Flow requests across multiple web servers.

Copyright © 2010-2020 CloudBees, Inc.Online version published by CloudBees, Inc. under the Creative Commons Attribution-ShareAlike 4.0 license.CloudBees and CloudBees DevOptics are registered trademarks and CloudBees Core, CloudBees Flow, CloudBees Flow Deploy, CloudBees Flow DevOps Insight, CloudBees Flow DevOps Foresight, CloudBees Flow Release, CloudBees Accelerator, CloudBees Accelerator ElectricInsight, CloudBees Accelerator Electric Make, CloudBees CodeShip, CloudBees Jenkins Enterprise, CloudBees Jenkins Platform, CloudBees Jenkins Operations Center, and DEV@cloud are trademarks of CloudBees, Inc. Most CloudBees products are commonly referred to by their short names — Accelerator, Automation Platform, Flow, Deploy, Foresight, Release, Insight, and eMake — throughout various types of CloudBees product-specific documentation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Jenkins is a registered trademark of the non-profit Software in the Public Interest organization. Used with permission. See here for more info about the Jenkins project. The registered trademark Jenkins® is used pursuant to a sublicense from the Jenkins project and Software in the Public Interest, Inc. Read more at Apache, Apache Ant, Apache Maven, Ant and Maven are trademarks of The Apache Software Foundation. Used with permission. No endorsement by The Apache Software Foundation is implied by the use of these marks.Other names may be trademarks of their respective owners. Many of the designations used by manufacturers and sellers to distinguish their products are claimed as trademarks. Where those designations appear in this content, and CloudBees was aware of a trademark claim, the designations have been printed in caps or initial caps. While every precaution has been taken in the preparation of this content, the publisher and authors assume no responsibility for errors or omissions, or for damages resulting from the use of the information contained herein.