chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ari Rabkin (JIRA)" <j...@apache.org>
Subject [jira] Commented: (CHUKWA-305) Inconsistent time inputs
Date Wed, 17 Jun 2009 19:20:08 GMT

    [ https://issues.apache.org/jira/browse/CHUKWA-305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12720845#action_12720845
] 

Ari Rabkin commented on CHUKWA-305:
-----------------------------------

This is indeed a problem.  

A couple questions to guide the solution process.

1) Can we alter the Hadoop log format?  We do, after all, have a custom log4j appender.

2) Can an agent detect its own timezone?  

> Inconsistent time inputs
> ------------------------
>
>                 Key: CHUKWA-305
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-305
>             Project: Hadoop Chukwa
>          Issue Type: Bug
>          Components: data collection, Data Processors
>            Reporter: Jiaqi Tan
>
> Times in Job History logs are stored in UTC seconds from Epoch, but times in log-based
sources e.g. clienttrace, and the daemon (DataNode, TaskTracker, JobTracker, NameNode) logs
are in local timezones and in ISO-8601 strings, and do not have the timezone they are recorded
in. This leads to inconsistencies when trying to correlate data in time across log-based sources
and Job History data because the timezone of the data for the log-based sources which emit
times in human-readable strings do not record the timezone. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message