Increase Maximum Capacity of Agents for Execution Server

Products

• CA Release Automation - Release Operations Center (Nolio)
• CA Release Automation - DataManagement Server (Nolio)

Issue/Introduction

Summary: 

By default, a Release Automation (Nolio) execution server (NES) cannot have any more than 200 agents connected to it at a time.  This article will detail how to increase this limit and what considerations one should be mindful of when doing so.

Background:  

Some larger enterprise environments may require a large number of agents. When the number of agents connected to a single NES exceed the maximum capacity, various problems can occur, such as some agents dropping offline unexpectedly. The NES will report the following error in its nimi.log when over capacity:

DEBUG (KeepAliveManagerImpl.java:283) - Not updating [NodeInfo{nodeId=nid:[NodeName], hostname='[HostName]', addresses=[/x.x.x.x:6600], nodeType=NODE, version=x.x.x.xx}] - this supernode is over max capacity

Environment:  

This applies to all versions of Release Automation on all platforms. 

Instructions: 

Before increasing the maximum number of agents a single NES is allowed to have, the system administrator should take careful consideration regarding system resources.  The more agents a single NES has, the more resources (CPU, ram, JVM heap size, etc.) are required. Care should be taken not to allow more agents than the server can handle.  With this in mind, the following steps are required to increase the maximum number of agents allowed:

1. Navigate to the /conf directory within the Release Automation installation directory.
2. Open the nimi_config.xml file for editing.
3. Find the following settings:
   

   <server>

   <capacity>200</capacity> <!-- how much nodes to accept-->

   <warn-capacity>200</warn-capacity> <!-- over this limit new connecting

   nodes will be asked to seek another supernode-->

   </server>

4. Change the value for <capacity> to the maximum number of agents desired (the default is 200).
5. It is likewise recommended to change the <warn-capacity> value to the same value.
6. Ensure no jobs are currently running on the NES.
7. Restart the NES.

 

Environment

Release: NOLNAC99000-6.1-Nolio-Automation Center
Component: