drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF GitHub Bot (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-4935) Allow drillbits to advertise a configurable host address to Zookeeper
Date Wed, 09 Nov 2016 20:10:58 GMT

    [ https://issues.apache.org/jira/browse/DRILL-4935?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15651922#comment-15651922
] 

ASF GitHub Bot commented on DRILL-4935:
---------------------------------------

Github user harrisonmebane commented on the issue:

    https://github.com/apache/drill/pull/647
  
    I have tested this fix manually, in the following way:
    
    * Deploy Drill in Docker containers on an existing cluster on AWS, with the line 
    ```export DRILL_HOST_NAME=`curl http://169.254.169.254/latest/meta-data/local-ipv4` ```
in `drill-env.sh`, to ensure that the variable is populated with the host machine's IP.
    * Start a Drill session in the docker container and run `select * from sys.drillbits;`.
 The result was: 
    ```
    +----------------+------------+---------------+------------+----------+
    |    hostname    | user_port  | control_port  | data_port  | current  |
    +----------------+------------+---------------+------------+----------+
    | 172.31.21.207  | 31010      | 31011         | 31012      | false    |
    | 172.31.29.130  | 31010      | 31011         | 31012      | true     |
    | 172.31.22.200  | 31010      | 31011         | 31012      | false    |
    +----------------+------------+---------------+------------+----------+
    ```
    * On one of the drillbits, comment out the `DRILL_HOST_NAME` line in `drill-env.sh`, unset
the variable, and restart the drillbit.
    * Log into Drill shell again and run `select * from sys.drillbits;`  Result is now:
    ```
    +----------------+------------+---------------+------------+----------+
    |    hostname    | user_port  | control_port  | data_port  | current  |
    +----------------+------------+---------------+------------+----------+
    | 172.31.22.200  | 31010      | 31011         | 31012      | false    |
    | a53b37888f62   | 31010      | 31011         | 31012      | true     |
    | 172.31.29.130  | 31010      | 31011         | 31012      | false    |
    +----------------+------------+---------------+------------+----------+
    ```
    * Running queries that require the other nodes results in a `Error: SYSTEM ERROR: UnresolvedAddressException`,
indicating that the new address registered on Zookeeper no longer works
    



> Allow drillbits to advertise a configurable host address to Zookeeper
> ---------------------------------------------------------------------
>
>                 Key: DRILL-4935
>                 URL: https://issues.apache.org/jira/browse/DRILL-4935
>             Project: Apache Drill
>          Issue Type: New Feature
>          Components: Execution - RPC
>    Affects Versions: 1.8.0
>            Reporter: Harrison Mebane
>            Priority: Minor
>             Fix For: Future
>
>
> There are certain situations, such as running Drill in distributed Docker containers,
in which it is desirable to advertise a different hostname to Zookeeper than would be output
by INetAddress.getLocalHost().  I propose adding a configuration variable 'drill.exec.rpc.bit.advertised.host'
and passing this address to Zookeeper when the configuration variable is populated, otherwise
falling back to the present behavior.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message