Data loaders gather cluster operation data and load it into tables in a relational database containing raw data. Data loaders are controlled by the Platform loader controller (plc) service.
There are logging levels that determine the detail of messages that the data loaders 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, data loaders log messages of INFO level or higher (that is, all INFO, WARN, ERROR, and FATAL messages).
The data loader log files are located in the dataloader subdirectory of the log directory:
Data loaders gather data from data sources at regular intervals. The following are lists of the data loaders, the specific loader controller configuration file (plc_*.xml), and the default behavior:
The loader controller service controls the scheduling of the data loaders. The data loaders store LSF and license 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 data loaders and other components.
After editing the loader controller configuration files, restart the loader controller for your changes to take effect. The specific loader controller configuration file (plc_*.xml) depends on the type of data loader.
These files are located in the loader controller configuration directory:
The data loaders only log messages of the same or lower level of detail as log_level. Therefore, if you change the log level to ERROR, the data loaders will only log ERROR and FATAL messages.