You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ambari.apache.org by Aleksandr Kovalenko <ak...@hortonworks.com> on 2014/03/20 17:31:10 UTC

Review Request 19470: Mirroring: surface error messages from Falcon

-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19470/
-----------------------------------------------------------

Review request for Ambari and Alexandr Antonenko.


Bugs: AMBARI-5162
    https://issues.apache.org/jira/browse/AMBARI-5162


Repository: ambari


Description
-------

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 following:
{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 environment.
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 10.240.114.245</message><requestId>ed258530-617a-4b77-bab3-508f9cdd8eb9</requestId></result>
{noformat}


Diffs
-----

  ambari-web/app/controllers/main/mirroring/edit_dataset_controller.js cbf21d1 
  ambari-web/app/controllers/main/mirroring/manage_clusters_controller.js cdab86e 

Diff: https://reviews.apache.org/r/19470/diff/


Testing
-------

2536 tests complete (862 ms)


Thanks,

Aleksandr Kovalenko


Re: Review Request 19470: Mirroring: surface error messages from Falcon

Posted by Alexandr Antonenko <hi...@gmail.com>.
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/19470/#review37900
-----------------------------------------------------------

Ship it!


Ship It!

- Alexandr Antonenko


On March 20, 2014, 4:31 p.m., Aleksandr Kovalenko wrote:
> 
> -----------------------------------------------------------
> This is an automatically generated e-mail. To reply, visit:
> https://reviews.apache.org/r/19470/
> -----------------------------------------------------------
> 
> (Updated March 20, 2014, 4:31 p.m.)
> 
> 
> Review request for Ambari and Alexandr Antonenko.
> 
> 
> Bugs: AMBARI-5162
>     https://issues.apache.org/jira/browse/AMBARI-5162
> 
> 
> Repository: ambari
> 
> 
> Description
> -------
> 
> 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 following:
> {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 environment.
> 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 10.240.114.245</message><requestId>ed258530-617a-4b77-bab3-508f9cdd8eb9</requestId></result>
> {noformat}
> 
> 
> Diffs
> -----
> 
>   ambari-web/app/controllers/main/mirroring/edit_dataset_controller.js cbf21d1 
>   ambari-web/app/controllers/main/mirroring/manage_clusters_controller.js cdab86e 
> 
> Diff: https://reviews.apache.org/r/19470/diff/
> 
> 
> Testing
> -------
> 
> 2536 tests complete (862 ms)
> 
> 
> Thanks,
> 
> Aleksandr Kovalenko
> 
>