falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanth Sundarrajan (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-26) Pipeline Monitor addition
Date Fri, 03 Jan 2014 16:59:51 GMT

    [ https://issues.apache.org/jira/browse/FALCON-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861667#comment-13861667
] 

Srikanth Sundarrajan commented on FALCON-26:
--------------------------------------------

To iterate over each of the coord action just as in instance status to produce consolidate
summary may be sub optimal. Can you please examine if there are any options available in the
underlying scheduler to get consolidated status?

> Pipeline Monitor addition
> -------------------------
>
>                 Key: FALCON-26
>                 URL: https://issues.apache.org/jira/browse/FALCON-26
>             Project: Falcon
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 0.3
>            Reporter: Samarth Gupta
>            Assignee: Suhas Vasu
>         Attachments: FALCON-26.patch
>
>   Original Estimate: 120h
>  Remaining Estimate: 120h
>
> adding features to falcon get instance status api to return summarized result for a given
process. This will enable user to specify start and end time of instance and in return will
get summarized result grouped based on there status. and number of instance belonging to those
status



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message