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-1339) List feed entities shows scheduled Feed entities as submitted
Date Thu, 03 Sep 2015 15:47:45 GMT

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

Srikanth Sundarrajan commented on FALCON-1339:
----------------------------------------------

With dry-run enabled we should see very less failures at a coord level. We should be seeing
more of SUCCEEDED or DONEWITHERROR. Under normal circumstances I dont expect any coord / bundle
to end up in FAILED/KILLED state given that there is enough gating at falcon level before
schedule is attempted. 

If we do want to reflect the status of the bundle's failed/killed and not reflect instance
status, It should be ok to include these additional statuses.

> List feed entities shows scheduled Feed entities as submitted
> -------------------------------------------------------------
>
>                 Key: FALCON-1339
>                 URL: https://issues.apache.org/jira/browse/FALCON-1339
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.6.1
>            Reporter: Balu Vellanki
>            Assignee: Balu Vellanki
>            Priority: Critical
>
> To reproduce this issue, please do the following steps.
> - Submit a source cluster named primaryCluster.
> - Submit a feed.
> {code}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
> <feed name="rawEmailFeed" description="Raw customer email feed" xmlns="uri:falcon:feed:0.1">
>     <tags>externalSystem=USWestEmailServers</tags>
>     <groups>churnAnalysisDataPipeline</groups>
>     <frequency>hours(1)</frequency>
>     <timezone>UTC</timezone>
>     <late-arrival cut-off="hours(1)"/>
>     <clusters>
>         <cluster name="primaryCluster" type="source">
>             <validity start="2015-07-22T01:00Z" end="2015-07-22T03:00Z"/>
>             <retention limit="days(90)" action="delete"/>
>         </cluster>
>     </clusters>
>     <locations>
>         <location type="data" path="/user/ambari-qa/falcon/demo/primary/input/enron/${YEAR}-${MONTH}-${DAY}-${HOUR}"/>
>         <location type="stats" path="/"/>
>         <location type="meta" path="/"/>
>     </locations>
>     <ACL owner="ambari-qa" group="users" permission="0x755"/>
>     <schema location="/none" provider="/none"/>
> </feed>
> {code}
> - Schedule this feed.
> - A bundle is not created for this feed because,
> {code}
> "Feed Retention is not applicable as Feed's end time for cluster primaryCluster is not
in the future"
> {code}
> Since there are no running bundles on the cluster, the status of this feed will always
be shown as "SUBMITTED" even after being scheduled. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message