You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Jiaqi Tan (JIRA)" <ji...@apache.org> on 2009/09/23 03:13:15 UTC
[jira] Created: (CHUKWA-394) FSMBuilder checks for wrong tag in
TaskTracker ClientTrace
FSMBuilder checks for wrong tag in TaskTracker ClientTrace
----------------------------------------------------------
Key: CHUKWA-394
URL: https://issues.apache.org/jira/browse/CHUKWA-394
Project: Hadoop Chukwa
Issue Type: Bug
Components: Data Processors
Affects Versions: 0.3.0
Reporter: Jiaqi Tan
Assignee: Jiaqi Tan
Fix For: 0.3.0
TaskTracker ClientTrace data extraction looks for the reduce ID in the wrong tag
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (CHUKWA-394) FSMBuilder checks for wrong tag in
TaskTracker ClientTrace
Posted by "Jiaqi Tan (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/CHUKWA-394?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jiaqi Tan resolved CHUKWA-394.
------------------------------
Resolution: Invalid
Made a mistake, turns out this was a problem with the logging at the source, not with the processing. The cluster which generated the logs did not have the new logging patches applied.
> FSMBuilder checks for wrong tag in TaskTracker ClientTrace
> ----------------------------------------------------------
>
> Key: CHUKWA-394
> URL: https://issues.apache.org/jira/browse/CHUKWA-394
> Project: Hadoop Chukwa
> Issue Type: Bug
> Components: Data Processors
> Affects Versions: 0.3.0
> Reporter: Jiaqi Tan
> Assignee: Jiaqi Tan
> Fix For: 0.3.0
>
>
> TaskTracker ClientTrace data extraction looks for the reduce ID in the wrong tag
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.