2 woshiqianqu woshiqianqu 于 2016.05.11 11:40 提问

impala catalog起不来 报错如下

log4j:WARN No appenders could be found for logger (org.apache.hadoop.metrics2.lib.MutableMetricsFactory).
log4j:WARN Please initialize the log4j system properly.
log4j:WARN See http://logging.apache.org/log4j/1.2/faq.html#noconfig for more info.
E0511 11:33:51.635500 13048 catalog.cc:66] java.lang.IllegalStateException: java.lang.NumberFormatException: For input string: "0s"
at com.cloudera.impala.catalog.MetaStoreClientPool$MetaStoreClient.(MetaStoreClientPool.java:59)
at com.cloudera.impala.catalog.MetaStoreClientPool$MetaStoreClient.(MetaStoreClientPool.java:49)
at com.cloudera.impala.catalog.MetaStoreClientPool.addClients(MetaStoreClientPool.java:116)
at com.cloudera.impala.catalog.Catalog.(Catalog.java:89)
at com.cloudera.impala.catalog.CatalogServiceCatalog.(CatalogServiceCatalog.java:102)
at com.cloudera.impala.service.JniCatalog.(JniCatalog.java:78)
Caused by: java.lang.NumberFormatException: For input string: "0s"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.parseLong(Long.java:483)
at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1113)
at org.apache.hadoop.hive.conf.HiveConf.getLongVar(HiveConf.java:913)
at org.apache.hadoop.hive.conf.HiveConf.getLongVar(HiveConf.java:926)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:351)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.(HiveMetaStore.java:289)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.(RetryingHMSHandler.java:56)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.getProxy(RetryingHMSHandler.java:61)
at org.apache.hadoop.hive.metastore.HiveMetaStore.newHMSHandler(HiveMetaStore.java:4014)
at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.(HiveMetaStoreClient.java:120)
at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.(HiveMetaStoreClient.java:103)
at com.cloudera.impala.catalog.MetaStoreClientPool$MetaStoreClient.(MetaStoreClientPool.java:56)
... 5 more

1个回答

silehaixianghuirenj
silehaixianghuirenj   2016.10.08 01:25

51.635500 13048 catalog.cc:66] java.lang.IllegalStateException: java.lang.NumberFormatException: For input string: "0s"
at com.cloudera.impala.catalog.MetaStoreClientPool$MetaStoreClient.(MetaStoreClientPool.java:59)
at com.cloudera.impala.catalog.MetaStoreClientPool$MetaStoreClient.(MetaStoreClientPool.java:49)
at com.cloudera.impala.catalog.MetaStoreClientPool.addClients(MetaStoreClientPool.java:116)
at com.cloudera.impala.catalog.Catalog.(Catalog.java:89)
at com.cloudera.impala.catalog.CatalogServiceCatalog.(CatalogServiceCatalog.java:102)
at com.cloudera.impala.service.JniCatalog.(JniCatalog.java:78)
Caused by: java.lang.NumberFormatException: For input string: "0s"
at java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
at java.lang.Long.parseLong(Long.java:441)
at java.lang.Long.parseLong(Long.java:483)
at org.apache.hadoop.conf.Configuration.getLong(Configuration.java:1113)
at org.apache.hadoop.hive.conf.HiveConf.getLongVar(HiveConf.java:913)
at org.apache.hadoop.hive.conf.HiveConf.getLongVar(HiveConf.java:926)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.init(HiveMetaStore.java:351)
at org.apache.hadoop.hive.metastore.HiveMetaStore$HMSHandler.(HiveMetaStore.java:289)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.(RetryingHMSHandler.java:56)
at org.apache.hadoop.hive.metastore.RetryingHMSHandler.getProxy(RetryingHMSHandler.java:61)
at org.apache.hadoop.hive.metastore.HiveMetaStore.newHMSHandler(HiveMetaStore.java:4014)
at org.apache.hadoop.hive.metastore.HiveMetaStoreClient.(HiveMet

Csdn user default icon
上传中...
上传图片
插入图片
准确详细的回答,更有利于被提问者采纳,从而获得C币。复制、灌水、广告等回答会被删除,是时候展现真正的技术了!
其他相关推荐
Impala源码解析 - 了解Impala Catalog加载过程和到底加载了什么
在一个大型的应用系统,每天都有上百亿甚至上千亿的数据需要加载到Hadoop中,随着数据量达到海量的级别,原本可以轻松搞定的事情,现在都变得非常棘手,不管是在Oracle中还是以Impala作为实时查询引擎的Hadoop中,都会遇到很多让你日思夜想,难以入眠的问题。
Impala之Catalogd进程
Catalogd进程是Impala中用来传递Impala SQL导致的元数据变化的组件,它把这些变化传递给集群中所有的节点。一个集群中只需要一个节点上有这个守护进程,因为请求是通过Statestore传递的,因此Statestored和Catalogd 服务应当运行在同一节点上。
安装和使用impala出现的问题及解决方法
1、没有成功安装impala-server impala-state-store  impala-catalog:       修改错误的/etc/yum.repos.d 2、找不到JDO什么FactoryManager类:修改jar包路径 3 、mysql-connector-java-5.1.30-bin.jar 放进/var/lib/impala/中 4、修改hive-site.xm
Impala源码之订阅发布系统的实现
众所周知,Impala包含三个模块,分别是impalad、catalogd和statestored,其中statestored模块的作用是实现一个业务无关的订阅(Subscribe)发布(Publish)系统,catalod和impalad中的部分消息传递需要通过statestored传递,为什么要使用这样一个业务无关的服务来传递消息呢?下面我们来揭开它神秘的面纱。
Impala之StateStore进程
StateStore是用来检查Impala集群中所有节点守护进程Impalad健康状况的守护进程,并且将它的发现持续性的发送给这些Impala守护进程。
Impala实践之十四:一次Impala节点故障记录(不能启动)
前言Impala集群中有两台机器的Impala Daemon不能正常启动,记录一下整个过程和解决方式。过程阶段一Impala集群的状态开始飘红,有两台节点不能正常使用。这时候发现集群里面有十多个任务正在运行,任务执行时间很长,情况非常不正常。看了一下sql的内容,有几个sql的确比较耗资源。阶段二此时,我先通知不要提交sql,给修复问题留点时间。正在重启不健康的节点,群里面就有人继续提交了不合理的s
Impala重要组件介绍
Impala重要组件 1.Impala Daemon The core Impala component is a daemon process that runs on each DataNode of the cluster, physically represented by the impalad process. Impala的核心组件是运行在各个节点上面的
Impala之Impalad进程
Impalad进程是Impala的核心组件,它是运行在集群中每个Impala节点上的一个守护进程。它主要负责:1、从HDFS或HBase中读、写数据;2、接收来自JDBC、Impala Shell等客户端命令;3、并行化执行查询语句,分发到Impala集群中其它节点,并将查询中间结果汇报到中央协调节点Impalad进程;4、定时与statestore通讯,以确定哪些节点是健康的,可以接受新的工作;5、接收catalogd守护进程(Impala 1.2中引入)的广播,广播信息包括集群中任意Impala节点上创
Impala实践之四:记一次Impala报错的处理和分析过程
前言impala集群出错的一次记录和解决方法以及解决思路。错误记录错误信息Memory limit exceeded Cannot perform hash aggregation. Partitioned input data too many times. This could mean there is too much skew in the data or the memory limit
Impala简介(整理)
Impala是Cloudera公司主导开发的新型查询系统,它提供SQL语义,能查询存储在Hadoop的HDFS和HBase中的PB级大数据。已有的Hive系统虽然也提供了SQL语义,但由于Hive底层执行使用的是MapReduce引擎,仍然是一个批处理过程,难以满足查询的交互性。相比之下,Impala的最大特点也是最大卖点就是它的快速。