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/07/14 22:49:14 UTC

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

SALSA State-machine Generation Driver
-------------------------------------

                 Key: CHUKWA-348
                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
             Project: Hadoop Chukwa
          Issue Type: New Feature
          Components: Data Processors
    Affects Versions: 0.3.0
            Reporter: Jiaqi Tan
            Assignee: Jiaqi Tan
            Priority: Critical
             Fix For: 0.3.0


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.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Jiaqi Tan (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CHUKWA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731120#action_12731120 ] 

Jiaqi Tan commented on CHUKWA-348:
----------------------------------

More of a "coming soon" and "I will work on it" feature, I am anticipating this will be completed only in early August.

> SALSA State-machine Generation Driver
> -------------------------------------
>
>                 Key: CHUKWA-348
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>    Affects Versions: 0.3.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Critical
>             Fix For: 0.3.0
>
>   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.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Eric Yang (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/CHUKWA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12731124#action_12731124 ] 

Eric Yang commented on CHUKWA-348:
----------------------------------

The extension should reference to MetricDataLoader instead of AbstractDataLoader.  This ensures that the analyzed data would be loaded into database.  
Thanks

> SALSA State-machine Generation Driver
> -------------------------------------
>
>                 Key: CHUKWA-348
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>    Affects Versions: 0.3.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Critical
>             Fix For: 0.3.0
>
>   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.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CHUKWA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ari Rabkin updated CHUKWA-348:
------------------------------

    Fix Version/s: 0.5.0
                       (was: 0.4.0)

> SALSA State-machine Generation Driver
> -------------------------------------
>
>                 Key: CHUKWA-348
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>    Affects Versions: 0.3.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Critical
>             Fix For: 0.5.0
>
>   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.
-
You can reply to this email to add a comment to the issue online.

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

Posted by "Ari Rabkin (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/CHUKWA-348?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ari Rabkin updated CHUKWA-348:
------------------------------

    Fix Version/s:     (was: 0.3.0)
                   0.4.0

> SALSA State-machine Generation Driver
> -------------------------------------
>
>                 Key: CHUKWA-348
>                 URL: https://issues.apache.org/jira/browse/CHUKWA-348
>             Project: Hadoop Chukwa
>          Issue Type: New Feature
>          Components: Data Processors
>    Affects Versions: 0.3.0
>            Reporter: Jiaqi Tan
>            Assignee: Jiaqi Tan
>            Priority: Critical
>             Fix For: 0.4.0
>
>   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.
-
You can reply to this email to add a comment to the issue online.