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
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
