Last Updated: 2015-06-01
Condition or Error
The logging level used by Tungsten Cluster creates a lot of
entries, including WARN,
this generates a lot of information that is difficult to find
the real errors and problems. How do i change the logging
level?
Causes
By default, Tungsten Cluster reports a lot of information and
detail, including INFO
and other levels of detail that may generate a lot of
information. For example:
INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717251 (SET @current_db_user := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717257 (SET @disabled_trigger := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717257 (SET @cols := ''...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717257 (SET @current_user_fk := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717257 (SET @current_db_user := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717259 (SET @disabled_trigger := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717259 (SET @cols := ''...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717259 (SET @current_user_fk := NULL...) INFO | jvm 1 | 2016/02/18 10:16:46 | 2016-02-18 15:16:46,789 [brm - remote-to-thl-0] WARN filter.ReplicateFilter » Ignoring query : No schema found for this query from event 4020717259 (SET @current_db_user := NULL...)
Rectifications
The logging level used to report status and other information, and that is written into the log, can be changed to reduce or lower the reporting level. To do this:
Edit the
~tungsten_home/tungsten/tungsten-replicator/conf/log4j.properties
Find the following line:
log4j.logger.com.continuent.tungsten.replicator.filter.ReplicateFilter=DEBUG, stdout
This will change the logging level so that only entries at
DEBUG and higher will be
output.