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

[jira] [Updated] (FALCON-1681) Improve logging for idempotent behaviour while scheduling entities.

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

Pallavi Rao updated FALCON-1681:
--------------------------------
    Summary: Improve logging for idempotent behaviour while scheduling entities.  (was: Native scheduler does not maintain idempotent behaviour while scheduling entities.)

> 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
(v6.3.4#6332)