Billy(Yiming) Liu commented on KYLIN-2027:

This is not a bug. According to hbase doc: 

      <description>Property from ZooKeeper's config zoo.cfg.
      The port at which the clients will connect.
      <description>Comma separated list of servers in the ZooKeeper Quorum.
      For example, "host1.mydomain.com,host2.mydomain.com,host3.mydomain.com".
      By default this is set to localhost for local and pseudo-distributed modes
      of operation. For a fully-distributed setup, this should be set to a full
      list of ZooKeeper quorum servers. If HBASE_MANAGES_ZK is set in 
      this is the list of servers which we will start/stop ZooKeeper on.

port should be set in 'hbase.zookeeper.property.clientPort', not 

> Error "connection timed out" occurs when zookeeper's port is set in 
> hbase.zookeeper.quorum of hbase-site.xml
> ------------------------------------------------------------------------------------------------------------
>                 Key: KYLIN-2027
>                 URL: https://issues.apache.org/jira/browse/KYLIN-2027
>             Project: Kylin
>          Issue Type: Bug
>          Components: Storage - HBase
>    Affects Versions: v1.5.4
>            Reporter: nichunen
>            Assignee: nichunen
>            Priority: Minor
>              Labels: patch
>             Fix For: v1.6.0
>         Attachments: KYLIN-2027.patch
> In our hadoop cluster, we specified ports of zk servers in 
> hbase.zookeeper.quorum of hbase-site.xml like 
>   <property>
>     <name>hbase.zookeeper.quorum</name>
>     <value>hadoop1:2181,hadoop2:2181,hadoop3:2181</value>
>   </property>
> And we get the error "ERROR [Thread-12] curator.ConnectionState:201 : 
> Connection timed out for connection string 
> (hadoop1:2181:2181,hadoop2:2181:2181,hadoop3:2181:2181) and timeout (15000) / 
> elapsed (15214)"
> I think 
> org.apache.kylin.storage.hbase.util.ZookeeperJobLock#getZKConnectString 
> should check whether it ends with a port before adding a port to the string.
> Attached is the patch.

This message was sent by Atlassian JIRA

Reply via email to