Tidal Enterprise Scheduler: How does the Balanced Agent List Work?

Available Languages

Updated:November 1, 2011

Document ID:113304

Bias-Free Language

The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.

Introduction

Prerequisites

Requirements

Components Used

Conventions

Problem

Related Information

Introduction

This article describes how a Balanced Agent List works.

Prerequisites

Requirements

There are no specific requirements for this document.

Components Used

The information in this document is based on the Tidal Enterprise Scheduler 5.3.1 or 6.x.

The information in this document was created from the devices in a specific lab environment. All of the devices used in this document started with a cleared (default) configuration. If your network is live, make sure that you understand the potential impact of any command.

Conventions

Refer to Cisco Technical Tips Conventions for more information on document conventions.

Problem

Often users complain that all jobs run on one agent in the Balanced Agent List rather than balancing amongst all agents in the agent list. How does the Balanced Agent List work?

From the Tidal Client Online help—A balanced agent list launches jobs on the agent that currently has the lightest load. Use this type of list with Tidal Enterprise Scheduler agents on platforms that provide load information.

In addition to the information on Online Help, here are more details. load information is sent back to the master every minute. This load, in addition to how many jobs are running, is also based on percentage of CPU. If you ran two jobs at the same time, which did not exceed the load, they both would run off of one agent. If, for example, you had something running on agent A that takes 20 percent of the CPU and Agent B had nothing running, at the time of the master deciding which agent to run a new job on, it would pick B because its load is lighter. If all things are equal, the master always picks the first agent on the list.