Configuring the Log Level and Log File Size

Scenarios

If you need to change the log level of logs, you can change the log level of FusionInsight Manager. For a specific service, you can change the log level and the log file size to prevent the failure in saving logs due to insufficient disk space.

Impact on the System

The services need to be restarted for the new configuration to take effect. During the restart, the services are unavailable.

Changing the FusionInsight Manager Log Level

1. Log in to the active management node as user omm.
2. Run the following command to switch to the required directory:

   cd ${BIGDATA_HOME}/om-server/om/sbin

3. Run the following command to change the log level:

   ./setLogLevel.shLog level parameters

   The log level parameters are as follows and are listed in descending order by priority: FATAL, ERROR, WARN, INFO, and DEBUG. A program prints logs higher than or equal to a specified level. The higher the log level is, the fewer logs are printed.

   • DEFAULT: After this parameter is set, the default log level is used.
   • FATAL: severity of a critical error log. After this parameter is set, only logs of the FATAL level is recorded.
   • ERROR: error log level. After this parameter is set, logs of the ERROR and FATAL levels are displayed.
   • WARN: warning log level. After this parameter is set, logs of the WARN, ERROR, and FATAL levels are recorded.
   • INFO (default): informational log level. After this parameter is set, logs of the INFO, WARN, ERROR, and FATAL levels are displayed.
   • DEBUG: debugging log level. After this parameter is set, logs of the DEBUG, INFO, WARN, ERROR, and FATAL levels are displayed.
   • TRACE: tracing log level. After this parameter is set, logs of the TRACE, DEBUG, INFO, WARN, ERROR, and FATAL levels are displayed.
   

   The log levels of components are different as defined in open-source code.

4. Download and view logs to verify that the log level settings take effect. For details, see Log.

Changing the Service Log Level and Log File Size

The KrbServer, LdapServer, and DBService do not support the modification of the service log level and log file size.

1. Log in to FusionInsight Manager.
2. Choose Cluster > Name of the desired cluster > Services.
3. Click a service in the service list. On the displayed page, switch to the Configurations tab page.
4. On the displayed page, click the All Configurations tab. Expand the role instance displayed on the left of the page. Click Log of the role to be modified.
5. Search for the parameter description and select the log level to be changed, or set the log file size in configuration page. The unit of the log file size is MB.
   

   • The system automatically deletes logs based on the configured log size. To save more information, set the log file size a larger value. To ensure the integrity of log files, you are advised to manually back up the log files to another directory based on the actual service traffic before the log files are cleared according to clearance rules.
   • Some services do not support the function of changing the log level on the GUI.

6. Click Save. In the Save Configuration dialog box, click OK.
7. Download and view logs to verify that the log level settings take effect.