falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ajay Yadava (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1495) In instance status list, show all runs for instances when requested by user
Date Mon, 11 Jan 2016 13:00:42 GMT

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

Ajay Yadava commented on FALCON-1495:

[~nperiwal] informed me in an offline discussion that he had synced up with [~pallavi.rao]
and the patch is good to go. Will commit it shortly.

> 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
>             Fix For: trunk
>         Attachments: FALCON-1495-v0.patch, FALCON-1495-v1.patch, FALCON-1495-v2.patch,
FALCON-1495-v3.patch, FALCON-1495-v4.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

View raw message