Uploaded image for project: 'IMPALA'
  1. IMPALA
  2. IMPALA-2782

Allow Impala Shell to connect directly to impalad when config with proxy load balancer and kerberos

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      Currently, Impala Shell cannot connect directly to Impalad if it's configured with a proxy load balancer and kerberos. In this configuration, Impalad will present a credential that uses the load balancer's host. Impala Shell expects the impalad host. This mismatch caused the failure.

      It is actually possible for the Impala Shell to expect a different host name in the credential. When setting up the SASL connection in sasl_factory(), we just need to set the load balancer's host in the sasl_client.setAttr("host").

      Attachments

        Issue Links

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            thundergun Vincent Tran
            alan@cloudera.com Alan Choi
            Votes:
            1 Vote for this issue
            Watchers:
            6 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment