falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Venkatesh Seetharam (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-813) Expose job id for running jobs in Falcon
Date Fri, 17 Oct 2014 20:39:34 GMT

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

Venkatesh Seetharam commented on FALCON-813:
--------------------------------------------

One other thing to do is to send a message in pre processing so we know when the job started
and make an entry into the graph db, use this state to drive queries.

Only lifecycle management functions should use the workflow engine so we do not overwhelm
the wf engine. 

> Expose job id for running jobs in Falcon
> ----------------------------------------
>
>                 Key: FALCON-813
>                 URL: https://issues.apache.org/jira/browse/FALCON-813
>             Project: Falcon
>          Issue Type: Improvement
>          Components: client
>            Reporter: Suhas Vasu
>            Assignee: Suhas Vasu
>         Attachments: FALCON-813.patch
>
>
> Currently we have no way of tracking a running job via Falcon.
> Suppose we wanna look at the task logs of a particular job, we have to use {{-logs}}
option via CLI. This option gives us the link of the logs after it has been copied to staging
directory. The logMover might fail and we may not get these logs.
> Also there is no way of checking the logs of running jobs via this option.
> Hence it would be really helpful if we expose the job url through CLI



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

Mime
View raw message