Turn Off YugabyteDB TServer INFO Message Logging

The YB-TServer service performs the actual input-output for end-user requests. It handles Data Manipulation Language (DML) statements such as INSERT, UPDATE, DELETE, and SELECT.

YB-TServer actions are logged and organized by error severity: FATAL, ERROR, WARNING, INFO.

The log level is defined by the –minloglevel gFlag which can be set to one of the following values: 0 (INFO), 1 (WARN), 2 (ERROR), 3 (FATAL), where 0 (INFO) is the default.

The YB-TServer processes are quite chatty and log ALOT of INFO messages. If you are only intertesed in non-INFO messages, you can turn them off.

Example:

				
					[root@Cloud_Server_0 ~]# yugabyted start | grep log
| Log Dir             : /root/var/logs                                                                     |

[root@Cloud_Server_0 ~]# grep "^I" /root/var/logs/tserver/yb-tserver.INFO | wc -l
624

Wow, there were 624 entries added to the YB-TServer log immediately after a start.

Now let’s see how many lines are written if we change the minimum log level to 1 (WARN).

				
					[root@Cloud_Server_0 ~]# yugabyted destroy
Stopped yugabyted using config /root/var/conf/yugabyted.conf.
Deleted logs at /root/var/logs.
Deleted data at /root/var/data.
Deleted conf at /root/var/conf.

[root@Cloud_Server_0 ~]# yugabyted start --tserver_flag="minloglevel=1" | grep log
| Log Dir             : /root/var/logs                                                                     |

[root@Cloud_Server_0 ~]# grep "^I" /root/var/logs/tserver/yb-tserver.INFO | wc -l
0

No INFO lines were written to TServer INFO log.

Have Fun!