You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@falcon.apache.org by "Narayan Periwal (JIRA)" <ji...@apache.org> on 2015/12/31 06:22:49 UTC

[jira] [Updated] (FALCON-1495) In instance status list, show all runs for instances when requested by user

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

Narayan Periwal updated FALCON-1495:
------------------------------------
    Attachment: FALCON-1495-v3.patch

> In instance status list, show all runs for instances when requested by user
> ---------------------------------------------------------------------------
>
>                 Key: FALCON-1495
>                 URL: https://issues.apache.org/jira/browse/FALCON-1495
>             Project: Falcon
>          Issue Type: Sub-task
>          Components: ease, general
>            Reporter: sandeep samudrala
>            Assignee: Narayan Periwal
>         Attachments: FALCON-1495-v0.patch, FALCON-1495-v1.patch, FALCON-1495-v2.patch, FALCON-1495-v3.patch
>
>
> Most of the times , when there are failures in the pipelines, retries run and the workflows might have got succeeded in sub sequential retry. But for end user to figure out why it has failed initially might be useful to understand for failures handling and SLA misses.
> As of now to figure out the same, its a tedious task to get such information by either going through oozie DB/logs or via the logs backed up in hdfs by the falcon postprocessing(which is 100% reliable as in few cases, falcon post processing might fail or for some reason if it couldn't back up the logs).
> In either case, Falcon should abstract the oozie client layer to be used by end user, and support all runs status to end user.



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