You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@kylin.apache.org by "xiangakun (JIRA)" <ji...@apache.org> on 2019/07/03 03:01:00 UTC

[jira] [Created] (KYLIN-4070) No logs print in kylin.log file and met error "Error: Could not find or load main class org.apache.hadoop.mapreduce.v2.app.MRAppMaster"

xiangakun created KYLIN-4070:
--------------------------------

             Summary: No logs print in kylin.log file and met error "Error: Could not find or load main class org.apache.hadoop.mapreduce.v2.app.MRAppMaster"
                 Key: KYLIN-4070
                 URL: https://issues.apache.org/jira/browse/KYLIN-4070
             Project: Kylin
          Issue Type: Bug
         Environment: apache-kylin-2.6.2-bin-hbase1x  hadoop-2.7.7   hbase-1.2.11    hive-2.3.4
            Reporter: xiangakun


Hello friends,

 

I am using kylin with version 2.6.2, and the relied components are lists below, I start the kylin server successfully and met the error "org.apache.kylin.rest.exception.InternalErrorException: org/apache/hadoop/hive/conf/HiveConf" when loading hive meta data. I updated the configuration from "export HBASE_CLASSPATH_PREFIX=${KYLIN_HOME}/conf:${KYLIN_HOME}/lib/*:${KYLIN_HOME}/ext/*:${HBASE_CLASSPATH_PREFIX}"  to "export HBASE_CLASSPATH_PREFIX=${KYLIN_HOME}/conf:${KYLIN_HOME}/lib/*:${KYLIN_HOME}/ext/*:{color:#FF0000}${hive_dependency}{color}:${HBASE_CLASSPATH_PREFIX}" in kylin.sh file. it did work fine. However, after this action,  I found no more messages could be produced in logs/kylin.log file. I removed kylin.log file, and after restarted the kylin server, kylin.log file was not created any more. It's  seems too stange.

What's more, when I create a cube and build it, the error happens in step 3, it shows "

Error: Could not find or load main class org.apache.hadoop.mapreduce.v2.app.MRAppMaster". 

 

In fact, I used the same configuration in yarn-site.xml and mapred-site.xml files with kylin version 2.1.0 for a long time, it worked fine and never met such error.

 

Does anyone meet the same problem before? Hope receive your kindly help soon.

 

Thanks in advance.

 

Best Regards

xiangakun

 

 



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