[jira] [Commented] (DRILL-4523) Add the IP address if we enable debug for org.apache.drill.exec.coord.zk

["Parth Chandra (JIRA)" <ji...@apache.org>]

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

Parth Chandra commented on DRILL-4523:
--------------------------------------

If the hostname was localhost.localdomain, then the ipaddress will likely be 127.0.0.1 which is just as useless.  As [~mandoskippy] mentioned, other than the case of a single node cluster there is no case where we need to allow localhost (or the loopback address) as legal values for a drillbit endpoint. 
For the one special case of a single node cluster, we can provide a config variable to allow the localhost name.

> Add the IP address if we enable debug for org.apache.drill.exec.coord.zk
> ------------------------------------------------------------------------
>
>                 Key: DRILL-4523
>                 URL: https://issues.apache.org/jira/browse/DRILL-4523
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components:  Server
>    Affects Versions: 1.6.0
>            Reporter: Arina Ielchiieva
>            Assignee: Arina Ielchiieva
>             Fix For: 1.7.0
>
>
> If we enable debug for org.apache.drill.exec.coord.zk in logback.xml, we only get the hostname and ports information. For example:
> {code}
> 2015-11-04 19:47:02,927 [ServiceCache-0] DEBUG o.a.d.e.c.zk.ZKClusterCoordinator - Cache changed, updating.
> 2015-11-04 19:47:02,932 [ServiceCache-0] DEBUG o.a.d.e.c.zk.ZKClusterCoordinator - Active drillbit set changed.  Now includes 2 total bits.  New active drillbits:
>  h3.poc.com:31010:31011:31012
>  h2.poc.com:31010:31011:31012
> {code}
> We need to know the IP address of each hostname to do further troubleshooting.
> Imagine if any drillbit registers itself as "localhost.localdomain" in zookeeper, we will never know where it comes from. Enabling IP address tracking can help this case.



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