falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pallavi Rao (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1681) Improve logging for idempotent behaviour while scheduling entities.
Date Tue, 22 Dec 2015 10:13:46 GMT

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

Pallavi Rao commented on FALCON-1681:

[~pavan kumar], submit is independent of the scheduler and is also idempotent So, currently,
it will say submit successful (even if it is already scheduled). Whether is that is user-friendly
or not is something we should argue in another JIRA :-).

> Improve logging for idempotent behaviour while scheduling entities.
> -------------------------------------------------------------------
>                 Key: FALCON-1681
>                 URL: https://issues.apache.org/jira/browse/FALCON-1681
>             Project: Falcon
>          Issue Type: Bug
>          Components: scheduler
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>            Assignee: Pallavi Rao
>             Fix For: 0.9
>         Attachments: FALCON-1681.patch
> Currently if an entity is scheduled once, user can schedule that entity any number of
times. Since scheduler is not changing any functionality for end users, it should show the
same behaviour. Although when a scheduled entity is scheduled again it fails with the following
error :
> {noformat}
> dataqa@lda01:/mnt/users/pragya/scheduler$ fep -schedule -name Native-2 -properties falcon.scheduler:oozie
> ERROR: Bad Request;ua1/Entity schedule failed for process: Native-2
> {noformat}

This message was sent by Atlassian JIRA

View raw message