I’m seeing a warning ‘This node is standing by in case the primary node fails over’ when I try to login to my Jenkins instance. However at other times login works fine.
- CloudBees CI (CloudBees Core) on traditional platforms - Client controller
- CloudBees CI (CloudBees Core) on traditional platforms - Operations Center
- CloudBees Jenkins Platform - Client controller
- CloudBees Jenkins Platform - Operations Center
CloudBees High Availability Plugin provides CloudBees Jenkins users the ability to configure a secondary instance as a failover node. The failover node is in passive mode which means that it will not respond as if it were an active node. ‘This node is standing by in case the primary node fails over’ is the response from the secondary (passive) node in a High-availability (HA) pair. You will see this message if you attempt to access the secondary node or if you have a Load balancer (or reverse proxy) which is incorrectly setup to balance requests evenly between the primary and secondary nodes.
To correct this, do not direct requests to the secondary (passive) node. As well, do not use the secondary node responses as indication of the health status of your Jenkins instance. The secondary node is in standby mode and is designed to be ready (in case of failover) to take over from the primary node. Jenkins HA is a failover system (i.e. active-passive system) and not an active-active system.