Uploaded image for project: 'Ambari'
  1. Ambari
  2. AMBARI-5162

Mirroring: surface error messages from Falcon

    XMLWordPrintableJSON

Details

    • Task
    • Status: Resolved
    • Critical
    • Resolution: Fixed
    • 1.5.1
    • 1.5.1
    • ambari-web
    • None

    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:

      <?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>
      

      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:

      <?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>
      

      Attachments

        1. AMBARI-5162.patch
          7 kB
          Aleksandr Kovalenko

        Activity

          People

            akovalenko Aleksandr Kovalenko
            akovalenko Aleksandr Kovalenko
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: