[ 
https://issues.apache.org/jira/browse/HIVE-18535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16339039#comment-16339039
 ] 

songqi commented on HIVE-18535:
-------------------------------

Very, very puzzled and surprised, I solved the problem.
I just moved hive-site.xml file to /opt/tez/conf directory, the problem is 
solved.
I do not understand why.

> Can not start LLAP
> ------------------
>
>                 Key: HIVE-18535
>                 URL: https://issues.apache.org/jira/browse/HIVE-18535
>             Project: Hive
>          Issue Type: Bug
>          Components: llap
>    Affects Versions: 2.1.1
>         Environment: OS: centos7.2
> hive 2.1.1
> hadoop 2.7.4
> tez 0.8.5
>            Reporter: songqi
>            Assignee: songqi
>            Priority: Major
>
> I can not start llap, I hope the community can help me solve this problem.
> I do not understand why this is?
> {code:java}
> [root@s3 hive]# bin/hive --service llap --name llap_service --instances 2 
> --size 1g --loglevel INFO --args "-XX:MaxMetaspaceSize=128m -verbose:class 
> -XX:+UseParNewGC -Xmn1g -XX:+UseConcMarkSweepGC -XX:-UseBiasedLocking 
> -XX:+PerfDisableSharedMem" --cache 1g --executors 1 --iothreads 10 
> --slider-am-container-mb 1024
> which: no hbase in 
> (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/root/bin)
> SLF4J: Class path contains multiple SLF4J bindings.
> SLF4J: Found binding in 
> [jar:file:/opt/hive/lib/log4j-slf4j-impl-2.4.1.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/opt/tez/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: Found binding in 
> [jar:file:/opt/hadoop/share/hadoop/common/lib/slf4j-log4j12-1.7.10.jar!/org/slf4j/impl/StaticLoggerBinder.class]
> SLF4J: See http://www.slf4j.org/codes.html#multiple_bindings for an 
> explanation.
> SLF4J: Actual binding is of type [org.apache.logging.slf4j.Log4jLoggerFactory]
> INFO cli.LlapServiceDriver: LLAP service driver invoked with 
> arguments=[-directory, /tmp/staging-slider-X7qu26, --name, llap_service, 
> --instances, 2, --size, 1g, --loglevel, INFO, --args, 
> -XX:MaxMetaspaceSize=128m -verbose:class -XX:+UseParNewGC -Xmn1g 
> -XX:+UseConcMarkSweepGC -XX:-UseBiasedLocking -XX:+PerfDisableSharedMem, 
> --cache, 1g, --executors, 1, --iothreads, 10, --slider-am-container-mb, 1024]
> INFO conf.HiveConf: Found configuration file file:/opt/hive/conf/hive-site.xml
> Failed: Unable to find required config file: hive-site.xml
> java.lang.Exception: Unable to find required config file: hive-site.xml
>       at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.run(LlapServiceDriver.java:181)
>       at 
> org.apache.hadoop.hive.llap.cli.LlapServiceDriver.main(LlapServiceDriver.java:104)
> INFO cli.LlapServiceDriver: LLAP service driver finished
> {code}
> {code:java}
> [root@s3 llap]# bin/llapDaemon.sh start starting llapdaemon, logging to 
> /tmp/llapDaemonLogs/llap-daemon-root-s3.ff.com.log and 
> /tmp/llapDaemonLogs/llap-daemon-root-s3.ff.com.out
> cat /tmp/llapDaemonLogs/llap-daemon-root-s3.ff.com.out   
> + exec /opt/java/bin/java -Dproc_llapdaemon -Xms4096m -Xmx4096m -server 
> -Djava.net.preferIPv4Stack=true -XX:NewRatio=8 -XX:+UseNUMA 
> -XX:+PrintGCDetails -verbose:gc -XX:+UseGCLogFileRotation 
> -XX:NumberOfGCLogFiles=4 -XX:GCLogFileSize=100M 
> -Xloggc:/tmp/llapDaemonLogs/gc.log -XX:+UseParallelGC 
> -Dlog4j.configurationFile=llap-daemon-log4j2.properties 
> -Dllap.daemon.log.dir=/tmp/llapDaemonLogs 
> -Dllap.daemon.log.file=llap-daemon-root-s3.ff.com.log 
> -Dllap.daemon.root.logger=console -Dllap.daemon.log.level=DEBUG -classpath 
> '/opt/hive/conf:/opt/hive/scripts/llap/lib/*:/opt/hive/scripts/llap/lib/tez/*:/opt/hive/scripts/llap/lib/udfs/*:.:/opt/hadoop/share/hadoop/*:/opt/hive/lib/*:/opt/tez/conf:/opt/tez/*:/opt/tez/lib/*:/opt/hive/lib:/opt/tez:opt/tez/lib'
>  org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon Error: Could not find or 
> load main class org.apache.hadoop.hive.llap.daemon.impl.LlapDaemon
> {code}
>  



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

Reply via email to