ambari-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aleksandr Kovalenko (JIRA)" <>
Subject [jira] [Commented] (AMBARI-5162) Mirroring: surface error messages from Falcon
Date Thu, 20 Mar 2014 16:32:54 GMT


Aleksandr Kovalenko commented on AMBARI-5162:

committed to trunk

> Mirroring: surface error messages from Falcon
> ---------------------------------------------
>                 Key: AMBARI-5162
>                 URL:
>             Project: Ambari
>          Issue Type: Task
>          Components: client
>    Affects Versions: 1.5.1
>            Reporter: Aleksandr Kovalenko
>            Assignee: Aleksandr Kovalenko
>            Priority: Critical
>             Fix For: 1.5.1
>         Attachments: AMBARI-5162.patch
> When errors are encountered, depending on the API call made:
> 1. An error popup shows "Bad Request" and nothing else.  Falcon API is indeed returning
error details, so we should show that.  For example, entering an invalid Oozie URL shows the
> {noformat}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><status>FAILED</status><message>Invalid
Workflow server or port: http://yusakum2-2.c.pramod-thangali.internal:11000
> Unable to reach Oozie server.</message><requestId>2e8320b4-7327-4278-99de-2292456a27c0</requestId></result>
> {noformat}
> 2. No error popup is shown at all.  I believe this happens when "submitAndSchedule"'s
schedule part fails (not 100%, please confirm).  In my case "hadoop.proxyuser.falcon.hosts"
was set to the  Falcon server host name, which won't work when mirroring data across clusters.
 Maybe set this to something invalid and see if this can be replicated in a single cluster
> The API error message was:
> {noformat}
> <?xml version="1.0" encoding="UTF-8" standalone="yes"?><result><status>FAILED</status><message>Unable
to create retention workflow
> Unauthorized connection for super-user: falcon from IP</message><requestId>ed258530-617a-4b77-bab3-508f9cdd8eb9</requestId></result>
> {noformat}

This message was sent by Atlassian JIRA

View raw message