[
https://issues.apache.org/jira/browse/TRAFODION-909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16388666#comment-16388666
]
Sandhya Sundaresan commented on TRAFODION-909:
----------------------------------------------
The issue still exists but is a more minor issue now. The Node Number is now
actually reported as a CPU number which is reported correctly. As fix we can
remove CPU number and report it as the Node Number so it is consistent with the
other logging components.
This is from monitor log
2018-03-06 05:03:16,195, INFO, MON, *Node Number: 2*,, PIN: 11987 , Process
Name: $MONITOR,,, TID: 16075, Message ID: 101011300, [CCluster::NodeTmReady],
Node activated! pnid=2, name=(devcdh-3.novalocal)
This is from sql log
2018-03-06 05:04:41,216, INFO, SQL.EXE, *Node Number: 0, CPU: 2*, PIN: 20751,
Process Name: $Z020GXW,,, An executor process is launched.
> LP Bug: 1412641 - log4cpp -- Node number in master*.log is always 0
> -------------------------------------------------------------------
>
> Key: TRAFODION-909
> URL: https://issues.apache.org/jira/browse/TRAFODION-909
> Project: Apache Trafodion
> Issue Type: Bug
> Components: sql-exe
> Reporter: Gao, Rui-Xian
> Assignee: Sandhya Sundaresan
> Priority: Major
>
> Node number in master*.log is always 0, tm.log has correct number.
> SQL>select [first 5] * from udf(event_log_reader('f')) where
> log_file_name='master_exec_0_7476.log';
> LOG_TS SEVERITY COMPONENT NODE_NUMBER
> CPU PIN PROCESS_NAME SQL_CODE QUERY_ID
>
> MESSAGE
>
> LOG_FILE_NODE LOG_FILE_NAME
>
> LOG_FILE_LINE PARSE_STATUS
> -------------------------- ---------- ------------------------ -----------
> ----------- ----------- ------------ -----------
> --------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------
> -------------
> --------------------------------------------------------------------------------------------------------------------------------
> ------------- ------------
> 2015-01-19 04:29:53.454000 INFO SQL.ESP 0
> 2 24361 $Z020JW1 NULL NULL
>
> An ESP process is launched.
>
> 0 master_exec_0_7476.log
> 1
> 2015-01-19 04:29:53.462000 INFO SQL.ESP 0
> 2 24360 $Z020JW0 NULL NULL
>
> An ESP process is launched.
>
> 0 master_exec_0_7476.log
> 2
> 2015-01-19 04:29:53.452000 INFO SQL.ESP 0
> 5 31881 $Z050R0W NULL NULL
>
> An ESP process is launched.
>
> 0 master_exec_0_7476.log
> 1
> 2015-01-19 04:35:23.101000 INFO SQL.ESP 0
> 5 1892 $Z0501J2 NULL NULL
>
> An ESP process is launched.
>
> 0 master_exec_0_7476.log
> 2
> 2015-01-19 04:29:53.454000 INFO SQL.ESP 0
> 2 24361 $Z020JW1 NULL NULL
>
> An ESP process is launched.
>
> 0 master_exec_0_7476.log
> 1
> --- 5 row(s) selected.
> SQL>select [first 5] * from udf(event_log_reader('f')) where log_file_name
> like 'tm%';
> LOG_TS SEVERITY COMPONENT NODE_NUMBER
> CPU PIN PROCESS_NAME SQL_CODE QUERY_ID
>
> MESSAGE
>
> LOG_FILE_NODE LOG_FILE_NAME
>
> LOG_FILE_LINE PARSE_STATUS
> -------------------------- ---------- ------------------------ -----------
> ----------- ----------- ------------ -----------
> --------------------------------------------------------------------------------------------------------------------------------
>
> --------------------------------------------------------------------------------------------------------------------------------
> -------------
> --------------------------------------------------------------------------------------------------------------------------------
> ------------- ------------
> 2015-01-19 03:42:19.803000 INFO TM 2
> 2 4052 $TM2 NULL NULL
>
> Message: DTM_TM_PROCESS_STARTUP
>
> 0 tm.log
> 1
> 2015-01-19 03:42:31.193000 INFO TM 2
> 2 4052 $TM2 NULL NULL
>
> Message: DTM_RECOV_SYSRECOV_COMPLETE
>
> 0 tm.log
> 2
> 2015-01-19 03:42:21.090000 INFO TM 5
> 5 10604 $TM5 NULL NULL
>
> Message: DTM_TM_PROCESS_STARTUP
>
> 0 tm.log
> 1
> 2015-01-19 03:42:31.216000 INFO TM 5
> 5 10604 $TM5 NULL NULL
>
> Message: DTM_RECOV_SYSRECOV_COMPLETE
>
> 0 tm.log
> 2
> 2015-01-19 03:42:19.803000 INFO TM 2
> 2 4052 $TM2 NULL NULL
>
> Message: DTM_TM_PROCESS_STARTUP
>
> 0 tm.log
> 1
> --- 5 row(s) selected.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
