Atanu Mishra created TRAFODION-2144:
---------------------------------------

             Summary: Trafodion should use the same time zone for timestamps in 
all component log files
                 Key: TRAFODION-2144
                 URL: https://issues.apache.org/jira/browse/TRAFODION-2144
             Project: Apache Trafodion
          Issue Type: Improvement
          Components: dtm
    Affects Versions: 2.0-incubating, 1.3-incubating
            Reporter: Atanu Mishra


Trafodion has various log files from different components. Currently, different 
components don't seem to always use the same time zone for timestamps in their 
log files. For example, as far as I can tell, DTM log file trafodion.dtm.log 
seems to be using UTC for its timestamps, while SQL log files such as 
master_exec_xxx.log seem to be using the local time set on the machine.

In such an example, if the machine time is set to PDT, the timestamps in 
master_exec_xxx.log would be in PDT and trafodion.dtm.log would be in UTC. This 
makes it harder to correlate the messages and reestablish the timeline between 
different components. I imagine eventually this will also make it so much 
harder to analyze customer's log files.

We should really make an effort for all components to use the same time zone in 
the log files across the board.

To Reproduce:
Set the machine time zone to something other than UTC. Check trafodion.dtm.log 
and master_exec_xxx.log in $MY_SQROOT/logs to see their time difference.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to