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) Native scheduler does not maintain idempotent behaviour while scheduling entities.
Date Tue, 22 Dec 2015 06:44:46 GMT

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

Pallavi Rao commented on FALCON-1681:
-------------------------------------

Investigated the issue. Native scheduler does maintain idempotent behavior. The issue was
with the WorkflowEngineFactory not returning the right workflow engine, which will be fixed
in FALCON-1683. 

Will keep this JIRA open to run a couple of tests and fix any issues that violate this behavior.

> 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