chukwa-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jiaqi Tan (JIRA)" <>
Subject [jira] Work logged: (CHUKWA-94) SALSA state-machine extraction from Hadoop logs
Date Tue, 22 Sep 2009 16:14:16 GMT


Jiaqi Tan logged work on CHUKWA-94:

                Author: Jiaqi Tan
            Created on: 22/Sep/09 09:12 AM
            Start Date: 22/Sep/09 09:12 AM
    Worklog Time Spent: 48h 
      Work Description: Completed state-machine generation

Issue Time Tracking

            Time Spent: 624h  (was: 576h)
    Remaining Estimate: 48h  (was: 96h)

> SALSA state-machine extraction from Hadoop logs
> -----------------------------------------------
>                 Key: CHUKWA-94
>                 URL:
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>         Attachments: tan.pdf
>   Original Estimate: 672h
>          Time Spent: 624h
>  Remaining Estimate: 48h
> This is a proposed feature addition to extract state-machine views from Hadoop's logs
(TaskTracker, JobTracker, and DataNode currently supported, NameNode soon). These views are
as described in and will
enable analysis and diagnosis algorithms to be built on top of them.
> Building a full SALSA view involves two steps:
> 1. Incrementally parsing log entries on a per-node basis to extract states (line-by-line
reading, assuming the entire log file from a given node is available to the same process)
> 2. "Stitching" and correlating states across all logs (across nodes and across types)
to build a full state machine.
> My idea is to add SALSA as two jobs in the demux stage, with the first parsing job in
demux, and either having: 
> (a) the parsing job write its output to the permanent store with the correlating job
reading/writing from/to the permanent store, or 
> (b) the parsing job write its output back to the sinkfile and having the correlating
job reading from the sink file and writing to the permanent store.

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

View raw message