Loader controller

The Platform loader controller (plc) controls the data loaders that gather data from the system and writes the data into the relational database containing raw data.

About the loader controller

The loader controller manages the data loaders by controlling the schedule in which each data loader gathers data.

Logging levels

There are logging levels that determine the detail of messages that the PERF services record in the log files. In decreasing level of detail, these levels are ALL (all messages), TRACE, DEBUG, INFO, WARN, ERROR, FATAL, and OFF (no messages).

By default, the PERF services log messages of INFO level or higher (that is, all INFO, WARN, ERROR, and FATAL messages).

The loader controller log file is located in the log directory:

  • UNIX: $PERF_LOGDIR

  • Windows: %PERF_LOGDIR%

Default behavior

The loader controller service starts automatically when the master host starts up if you have the loader controller registered as an RC.

Loader controller interactions

The loader controller service controls the scheduling of the data loaders. Sampling and retrieving data loaders request cluster operation data from the data tables through the node data sources while other data loaders obtain it directly from the data tables through the node data sources. The data loaders store this data into data tables through the node data sources. Each data loader contains data that is stored in specific data tables in the database.

The following diagram illustrates the interaction between the loader controller and other components.

Configuration to modify loader controller behavior


Action

Configuration files

Parameter and syntax

Specify the default log level of your plc log file.

log4j.properties

File location:

  • UNIX: $PERF_CONFDIR
  • Windows: %PERF_CONFDIR%

log4j.logger.com.platform.perf.dataloader=log_level, com.platform.perf.dataloader

where

  • log_level is the default log level of your loader controller log files.

The loader controller only logs messages of the same or lower level of detail as log_level. Therefore, if you change the log level to ERROR, the loader controller will only log ERROR and FATAL messages.


Loader controller actions

Actions on the loader controller service

Note:

To stop or start the plc service, you must run the commands on the local host running the plc service.


Action

Command line

View the status of the plc and other PERF services.

perfadmin list

Stop the plc service.

perfadmin stop plc

Start the plc service.

perfadmin start plc


Actions to change the loader controller settings


Action

Command line

Dynamically change the log level of your loader controller log file (temporarily).

UNIX: plcclient.sh ‑l log_level

Windows: plcclient ‑l log_level

where

  • log_level is the log level of your loader controller log file.

If you restart the loader controller, these settings will revert back to the default level.

Note:

You must run this command on the local host running the plc service.