[
https://issues.apache.org/jira/browse/TRAFODION-2594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15973817#comment-15973817
]
ASF GitHub Bot commented on TRAFODION-2594:
-------------------------------------------
Github user sandhyasun commented on a diff in the pull request:
https://github.com/apache/incubator-trafodion/pull/1068#discussion_r112096641
--- Diff: core/sqf/conf/log4cxx.trafodion.masterexe.config ---
@@ -44,15 +45,15 @@
log4j.appender.mxoAppender.layout=org.apache.log4j.PatternLayout
log4j.appender.mxoAppender.layout.ConversionPattern=%d, %p, %c, %m%n
#MXOSRVR
+log4j.additive.mxoAppender=false
log4j.logger.MXOSRVR=ERROR, mxoAppender
# SQL
# uncomment the following line if you want to enable debug logging
-#log4j.logger.SQL.EXE=DEBUG
log4j.logger.SQL=INFO
log4j.logger.SQL.COMP=ERROR
-log4j.logger.SQL.EXE.Memory=INFO
-log4j.logger.SQL.ESP=ERROR
+log4j.logger.SQL.EXE=INFO
+log4j.logger.SQL.ESP=INFO
--- End diff --
Ok . But we are definitely changing behaviour already. There is a generic
method SQLMXLoggingArea::logExecRTInfo that uses INFO as the level. Am guessing
it could affect performance since it's used in BMO code paths. Not sure we
wnt the user to see all these messages by default. If you do a quick grep on
our code you can see what is being logged using this generic method.
> Trafodion logs the same message twice in most of its log4j and log4cxx logs
> ---------------------------------------------------------------------------
>
> Key: TRAFODION-2594
> URL: https://issues.apache.org/jira/browse/TRAFODION-2594
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-general
> Reporter: Selvaganesan Govindarajan
> Assignee: Selvaganesan Govindarajan
>
> For an example the SSMP process logs as follows
> 2016-12-11 01:33:11,994, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666,
> Process Name: $ZSM000,,, An ssmp process is launched.
> 2016-12-11 01:33:11,994, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666,
> Process Name: $ZSM000,,, An ssmp process is launched.
> 2016-12-12 02:55:02,141, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666,
> Process Name: $ZSM000,,,Early reply to query started message from
> $Z000MQW:466 to attempt graceful cancel of query
> MXID11000027856212348271213304001000000000206U3333300_415_S1. Explain
> Sequence Number: 0 FILE: ../runtimestats/CancelBroker.cpp LINE: 149
> 2016-12-12 02:55:02,141, INFO, SQL.SSMP, Node Number: 0, CPU: 0, PIN: 20666,
> Process Name: $ZSM000,,,Early reply to query started message from
> $Z000MQW:466 to attempt graceful cancel of query
> MXID11000027856212348271213304001000000000206U3333300_415_S1. Explain
> Sequence Number: 0 FILE: ../runtimestats/CancelBroker.cpp LINE: 149
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
