falcon-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pragya Mittal (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (FALCON-1681) Native scheduler does not maintain idempotent behaviour while scheduling entities.
Date Mon, 21 Dec 2015 12:33:46 GMT

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

Pragya Mittal commented on FALCON-1681:
---------------------------------------

[~pavan kumar] [~sandeep.samudrala] this change is not only in case of scheduling. All the
operations follow idempotent behaviour. If we are going to show the message , then we should
go forward and make the change for all the operations and not restrict it to scheduling only.

> Native scheduler does not maintain 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
>
> 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)

Mime
View raw message