[ 
https://issues.apache.org/jira/browse/KYLIN-3763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Travis Gu closed KYLIN-3763.
----------------------------
    Resolution: Invalid

> Kylin failed to start with CDH 6.1.0
> ------------------------------------
>
>                 Key: KYLIN-3763
>                 URL: https://issues.apache.org/jira/browse/KYLIN-3763
>             Project: Kylin
>          Issue Type: Bug
>    Affects Versions: v2.5.2
>            Reporter: Travis Gu
>            Priority: Major
>
> When I am trying to run kylin 2.5.2-bin-cdh57 with Cloudera CDH 6.1.0, the 
> check-env script doesn't print any error. But when I ran the kylin.sh start 
> command, the server failed to start.
> This is the error log:
> 2019-01-09 14:06:11,504 INFO [main-SendThread(iot-mes-host-a.novalocal:2181)] 
> zookeeper.ClientCnxn:1012 : Opening socket connection to server 
> iot-mes-host-a.novalocal/10.135.99.196:2181. Will not attempt to authenticate 
> using SASL (unknown error)
>  2019-01-09 14:06:11,504 INFO 
> [main-SendThread(iot-mes-host-a.novalocal:2181)] zookeeper.ClientCnxn:856 : 
> Socket connection established, initiating session, client: 
> /10.135.99.196:45868, server: iot-mes-host-a.novalocal/10.135.99.196:2181
>  2019-01-09 14:06:11,509 INFO [main] imps.CuratorFrameworkImpl:326 : Default 
> schema
>  2019-01-09 14:06:11,511 DEBUG [main] util.ZookeeperDistributedLock:143 : 
> [email protected] trying to lock 
> /kylin/kylin_metadata/create_htable/kylin_metadata/lock
>  2019-01-09 14:06:11,545 INFO 
> [main-SendThread(iot-mes-host-a.novalocal:2181)] zookeeper.ClientCnxn:1272 : 
> Session establishment complete on server 
> iot-mes-host-a.novalocal/10.135.99.196:2181, sessionid = 0x1682be976a90b96, 
> negotiated timeout = 60000
>  2019-01-09 14:06:11,550 INFO [main-EventThread] 
> state.ConnectionStateManager:237 : State change: CONNECTED
>  Exception in thread "main" java.lang.IllegalArgumentException: Failed to 
> find metadata store by url: kylin_metadata@hbase
>  at 
> org.apache.kylin.common.persistence.ResourceStore.createResourceStore(ResourceStore.java:98)
>  at 
> org.apache.kylin.common.persistence.ResourceStore.getStore(ResourceStore.java:110)
>  at 
> org.apache.kylin.rest.service.AclTableMigrationTool.checkIfNeedMigrate(AclTableMigrationTool.java:99)
>  at 
> org.apache.kylin.tool.AclTableMigrationCLI.main(AclTableMigrationCLI.java:43)
>  Caused by: java.lang.reflect.InvocationTargetException
>  at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
>  at 
> sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
>  at 
> sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
>  at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
>  at 
> org.apache.kylin.common.persistence.ResourceStore.createResourceStore(ResourceStore.java:92)
>  ... 3 more
>  Caused by: java.lang.NoSuchMethodError: 
> org.apache.curator.framework.api.CreateBuilder.creatingParentsIfNeeded()Lorg/apache/curator/framework/api/ProtectACLCreateModePathAndBytesable;
>  at 
> org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:146)
>  at 
> org.apache.kylin.storage.hbase.util.ZookeeperDistributedLock.lock(ZookeeperDistributedLock.java:167)
>  at 
> org.apache.kylin.storage.hbase.HBaseConnection.createHTableIfNeeded(HBaseConnection.java:328)
>  at 
> org.apache.kylin.storage.hbase.HBaseResourceStore.createHTableIfNeeded(HBaseResourceStore.java:112)
>  at 
> org.apache.kylin.storage.hbase.HBaseResourceStore.<init>(HBaseResourceStore.java:93)
>  ... 8 more
>  2019-01-09 14:06:11,565 INFO [close-hbase-conn] hbase.HBaseConnection:136 : 
> Closing HBase connections...
>  
> It looks like there are mutiple curators in the CDH hadoop and hbase class 
> path like 
> /opt/cloudera/parcels/CDH-6.1.0-1.cdh6.1.0.p0.770702/lib/hbase/lib/curator-framework-4.0.0.jar
>  and 
> /opt/cloudera/parcels/CDH-6.1.0-1.cdh6.1.0.p0.770702/lib/hadoop/lib/curator-framework-2.12.0.jar.
>  How to solve it?



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

Reply via email to