LLAP Error

[#1]

I am getting this error after enabling LLAP

HDP 2.5

Any pointers this below?

ERROR impl.LlapZookeeperRegistryImpl: Unable to start curator PathChildrenCache. Exception: {} org.apache.zookeeper.KeeperException$InvalidACLException: KeeperErrorCode = InvalidACL for /llap-sasl/user-hive   at org.apache.zookeeper.KeeperException.create(KeeperException.java:121) ~[zookeeper-3.4.6.2.5.0.0-1232.jar:3.4.6-1232--1]   at org.apache.zookeeper.KeeperException.create(KeeperException.java:51) ~[zookeeper-3.4.6.2.5.0.0-1232.jar:3.4.6-1232--1]   at org.apache.zookeeper.ZooKeeper.create(ZooKeeper.java:783) ~[zookeeper-3.4.6.2.5.0.0-1232.jar:3.4.6-1232--1]

[#2 · Accepted solution]

@Nube Technologies

Please check - the max container-size, and NM capacities. Looks like these parameters are set incorrectly on the cluster

Could you please check on the following item in your cluster.

1. Login to zookeeper client using the following command

zkCli.sh -server $hostName:2181 

Where $hostName = hostname of zookeeper server

2.Verify the ACLs set on the znode:

getAcl /llap-sasl/user-hive 

it should give the results like

'sasl,'hive 
: cdrwa 
'world,'anyone 
: r 

3. If the ACL's are not set propertly then manual Set ACLs on znode with comma separated

 
setAcl /llap-sasl/user-hive sasl:hive:cdrwa, world:anyone:r 

4.Verify the ACLs set on the znode:

getAcl /llap-sasl/user-hive

[#3]

@Njayakumar - thanks it worked

[#4]

Also please check - the max container-size, and NM capacities. Looks like these parameters are set incorrectly on the cluster

[#5]

This error normally indicates that the LLAP daemons itself have not started up. (It's been improved in more recent versions).

As pointed out in the previous reply, I'd suggest looking into the LLAP configs, NM parameters, AM sizes, and specifically the LLAP logs to figure out why the daemons did not start up.

More context: The ZK paths are created by the daemons when they start up. The hive llap client will not create the ZK path if it does not exist, and will end up running into this error if the daemons fail to start.