You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@chukwa.apache.org by "Eric Yang (Updated) (JIRA)" <ji...@apache.org> on 2012/03/31 05:25:21 UTC

[jira] [Updated] (CHUKWA-348) SALSA State-machine Generation Driver

     [ https://issues.apache.org/jira/browse/CHUKWA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Eric Yang updated CHUKWA-348:
-----------------------------

         Due Date: 7/Aug/09  (was: 7/Aug/09)
    Fix Version/s:     (was: 0.5.0)

0.5.0 has released, move to backlog.
                
> SALSA State-machine Generation Driver
> -------------------------------------
>
>                 Key: CHUKWA-348
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
>             Project: Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>    Affects Versions: 0.3.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Critical
>   Original Estimate: 504h
>  Remaining Estimate: 504h
>
> Currently the state-machine generation can be run only via a standalone call to bin/fsm.sh. The plan is to subclass the AbstractDataLoader to automatically call the state-machine generation when new data is available, and for this driver to automatically create output directories, and decide which FSMBuilder mapper class to call (based on the log type). Then, the state-machine records generated will be written to SeqFiles of ChukwaRecords that will get automatically routed to the correct repos/ directory (by the PostProcessManager), and the MDL will automatically load that to the database.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira