You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by dan young <da...@gmail.com> on 2019/09/04 19:11:24 UTC
LLAP woes...
Hello Hive,
We're trying to get LLAP running on Hive 3.1.2. We're having some issues
and I'm trying to figure out why the Hive Web UI is reporting a status of
LAUNCHING although it seems that the LLAP daemons are running. I can see
the LlapDaemon running, no errors the the llap container logs, nothing
jumps out, etc.... One thing I do noticed is that when we click on the Hive
web UI, we get an Unable to decode data path for zkpath... error in the
HiveServer2 log
2019-09-04T19:09:00,190 INFO [hiveserver2-web-42] utils.ServiceApiUtil:
Loading service definition from
hdfs://ip-10-199-1-216.ec2.internal:8020/user/hadoop/.yarn/services/looker-llap/looker-llap.json
2019-09-04T19:09:00,595 INFO [hiveserver2-web-42]
impl.LlapRegistryService: Using LLAP registry (client) type: Service
LlapRegistryService in state LlapRegistryService: STARTED
2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
Unable to decode data for zkpath:
/user-hadoop/looker-llap/workers/worker-0000000004. Ignoring from current
instances list..
2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
Unable to decode data for zkpath:
/user-hadoop/looker-llap/workers/worker-0000000006. Ignoring from current
instances list..
does anyone have some debugging tips and tricks? or insight into what to
look at next?
Re: LLAP woes...
Posted by dan young <da...@gmail.com>.
Hello Hive Users,
Does the version of zookeeper matter with these decode errors or is this
more of a jar issue? I can do a get in zkCli for these paths and do get
data for the LLAP instances.
hive 3.1.2
tried zookeeper: 3.4.12, 3.4.16, and 3.4.6. This error is when running
3.4.6.
2019-09-04T19:09:00,190 INFO [hiveserver2-web-42] utils.ServiceApiUtil:
Loading service definition from
hdfs://ip-10-199-1-216.ec2.internal:8020/user/hadoop/.yarn/services/looker-llap/looker-llap.json
2019-09-04T19:09:00,595 INFO [hiveserver2-web-42]
impl.LlapRegistryService: Using LLAP registry (client) type: Service
LlapRegistryService in state LlapRegistryService: STARTED
2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
Unable to decode data for zkpath:
/user-hadoop/looker-llap/workers/worker-0000000004. Ignoring from current
instances list..
2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
Unable to decode data for zkpath:
/user-hadoop/looker-llap/workers/worker-0000000006. Ignoring from current
instances list..
On Wed, Sep 4, 2019 at 1:11 PM dan young <da...@gmail.com> wrote:
> Hello Hive,
>
> We're trying to get LLAP running on Hive 3.1.2. We're having some issues
> and I'm trying to figure out why the Hive Web UI is reporting a status of
> LAUNCHING although it seems that the LLAP daemons are running. I can see
> the LlapDaemon running, no errors the the llap container logs, nothing
> jumps out, etc.... One thing I do noticed is that when we click on the Hive
> web UI, we get an Unable to decode data path for zkpath... error in the
> HiveServer2 log
>
> 2019-09-04T19:09:00,190 INFO [hiveserver2-web-42] utils.ServiceApiUtil:
> Loading service definition from
> hdfs://ip-10-199-1-216.ec2.internal:8020/user/hadoop/.yarn/services/looker-llap/looker-llap.json
>
> 2019-09-04T19:09:00,595 INFO [hiveserver2-web-42]
> impl.LlapRegistryService: Using LLAP registry (client) type: Service
> LlapRegistryService in state LlapRegistryService: STARTED
>
> 2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
> Unable to decode data for zkpath:
> /user-hadoop/looker-llap/workers/worker-0000000004. Ignoring from current
> instances list..
>
> 2019-09-04T19:09:00,746 ERROR [hiveserver2-web-42] impl.ZkRegistryBase:
> Unable to decode data for zkpath:
> /user-hadoop/looker-llap/workers/worker-0000000006. Ignoring from current
> instances list..
>
>
> does anyone have some debugging tips and tricks? or insight into what to
> look at next?
>
>