impala-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Brown (JIRA)" <>
Subject [jira] [Resolved] (IMPALA-5455) test infra cannot always contact TLS-enabled CM
Date Thu, 08 Jun 2017 15:53:18 GMT


Michael Brown resolved IMPALA-5455.
       Resolution: Fixed
    Fix Version/s: Impala 2.10.0

commit 488291022688e750342a3d8a775d2184e98b5822
Author: Michael Brown <>
Date:   Mon Jun 5 12:40:20 2017 -0700

    IMPALA-5455: test infra: default --cm-port based on --use-tls

    This patch sets the default --cm-port (for the CM ApiResource
    initialization) based on a new flag, --use-tls, which enables test infra
    to talk to CM clusters with TLS enabled. It is still possible to set a
    port override, but in general it will not be needed.



    Connected both to TLS-disabled and TLS-enabled CM instances. Before this
    patch, we would fail hard when trying to talk to the TLS-enabled CM

    Change-Id: Ie7dfa6c400687f3c5ccaf578fd4fb17dedd6eded
    Reviewed-by: Matthew Jacobs <>
    Tested-by: Impala Public Jenkins

> test infra cannot always contact TLS-enabled CM
> -----------------------------------------------
>                 Key: IMPALA-5455
>                 URL:
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Infrastructure
>    Affects Versions: Impala 2.9.0
>            Reporter: Michael Brown
>            Assignee: Michael Brown
>             Fix For: Impala 2.10.0
> The {{CmCluster}} class is set up to provide an abstraction for a CM-based cluster, but
it can't connect to a CM-based TLS cluster. It needs a few changes to the underlying CM API
call: to propagate the port and the TLS flag.

This message was sent by Atlassian JIRA

View raw message