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 06:08:46 UTC

[jira] [Commented] (FALCON-1680) Error message is not intuitive when entity schedule fails

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

Pallavi Rao commented on FALCON-1680:
-------------------------------------

This problem is not with the native scheduler but surfaced now because of the way the WebException was created. This is how it will be displayed after the fix:
{code}
ERROR: Bad Request;default/org.apache.falcon.FalconWebException::org.apache.falcon.FalconException: Entity schedule failed for process: pig-sleep
CausedBy: Entity pig-sleep is already scheduled on configured workflow engine.
{code}

> Error message is not intuitive when entity schedule fails
> ---------------------------------------------------------
>
>                 Key: FALCON-1680
>                 URL: https://issues.apache.org/jira/browse/FALCON-1680
>             Project: Falcon
>          Issue Type: Bug
>    Affects Versions: 0.9
>            Reporter: Pragya Mittal
>            Assignee: Pallavi Rao
>
> Entity can either be scheduled on oozie or native scheduler(They are mutually exclusive).
> Once entity is scheduled on oozie, if I try scheduling it on native scheduler then following error is thrown 
> {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}
> End user cannot infer much from this message as to what went wrong.



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