Support Questions
Find answers, ask questions, and share your expertise
Announcements
Alert: Welcome to the Unified Cloudera Community. Former HCC members be sure to read and learn how to activate your account here.

Spark llap - No service instances found in registry

Highlighted

Spark llap - No service instances found in registry

New Contributor

Hi All,

I have a already setup HDP 3.0 cluster having total 7 machines with 3 worker nodes.

I also installed Ranger to do security and a user already created on hive. Now I want to access hive table using spark. I have tried both using spark-shell and java code But both is getting same error.

I am using spark llap to provide username/password for hive. But spark got an Exception:"No service instances found in registry"

Log

scala> df.show

[Stage 0:> (0 + 0) / 1]18/12/10 17:08:51 WARN TaskSetManager: Stage 0 contains a task of very large size (423 KB). The maximum recommended task size is 100 KB.[Stage 0:> (0 + 1) / 1]18/12/10 17:08:55 WARN TaskSetManager: Lost task 0.0 in stage 0.0 (TID 0, s1.us-east4-c.c.asdf-224606.internal, executor 2): java.lang.RuntimeException: java.io.IOException: No service instances found in registry at com.hortonworks.spark.sql.hive.llap.HiveWarehouseDataReaderFactory.createDataReader(HiveWarehouseDataReaderFactory.java:66)

If my table is having 0 records than it works fine and show me a blank table but if records are greater than 0 than it gives me exception.

Thanks in advanced.

1 REPLY 1

Re: Spark llap - No service instances found in registry

Contributor

Hi @Bharat Bhushan,

It seems like there's something missconfigured in your spark-shell or spark-submit commands, which prevents a serviceRegistry creation and remains null:

https://github.com/apache/hive/blob/master/llap-ext-client/src/java/org/apache/hadoop/hive/llap/Llap...

Please refer to:

https://docs.hortonworks.com/HDPDocuments/HDP3/HDP-3.0.0/integrating-hive/content/hive_configure_a_s...

Verify both spark.sql.hive.hiveserver2.jdbc.url and spark.hadoop.hive.llap.daemon.service.hosts are correct.

Don't have an account?
Coming from Hortonworks? Activate your account here