0

I have successfully installed kudu on Ubuntu (Trusty) as per the official kudu documentations (see http://kudu.apache.org/docs/installation.html ). The setup has one node running master and tablet server and another node running the tablet server only. I am having issues installing impala-kudu without Cloudera Manager on the node running kudu master. I have followed CDH installation instructions on this (see http://www.cloudera.com/documentation/enterprise/latest/topics/cdh_ig_cdh5_install.html ) page until Step 3. I have avoided installing CDH with YARN and MRv1 as I don’t need to run any mapreduce jobs and will not be using hadoop. Impala-kudu and impala-kudu-shell installed without errors. When I launch the impala-shell it returns: 

Starting Impala Shell without Kerberos authentication
Error connecting: TTransportException, Could not connect to kudu_test:21000
***********************************************************************************
Welcome to the Impala shell. Copyright (c) 2015 Cloudera, Inc. All rights reserved.
(Impala Shell v2.7.0-cdh5-IMPALA_KUDU-cdh5 (48f1ad3) built on Thu Aug 18 12:15:44 PDT 2016)Want to know what version of Impala you're connected to? Run the VERSION command to
find out!
***********************************************************************************
[Not connected] >

I have tried to use the CONNECT option to connect to the kudu-master node without success. Both imapala-kudu and kudu are running on the same machine. Are there additional configuration settings which need to be changed or is hadoop and YARN a strict requirement to make impala-kudu work?

After running ps -ef | grep -i impalad I can confirm the impala daemon is not running. After navigating to the impala logs at ~/var/log/impala I find a few errors and warning files. Here is the output of impalad.ERROR:

Log file created at: 2016/09/13 13:26:24
Running on machine: kudu_test
Log line format: [IWEF]mmdd hh:mm:ss.uuuuuu threadid file:line] msg
E0913 13:26:24.084389  3021 logging.cc:118] stderr will be logged to this file.
E0913 13:26:25.406966  3021 impala-server.cc:249] Currently configured default filesystem: LocalFileSystem. fs.defaultFS (file:///) is not supported.ERROR: block location tracking is not properly enabled because
  - dfs.datanode.hdfs-blocks-metadata.enabled is not enabled.
  - dfs.client.file-block-storage-locations.timeout.millis is too low. It should be at least 10 seconds.

E0913 13:26:25.406990  3021 impala-server.cc:252] Aborting Impala Server startup due to improper configuration. Impalad exiting.

Maybe I need to revisit HDFS and the Hive Metastore to ensure I have these services configured properly?

4

1 回答 1

0

根据日志，impalad 退出是因为默认文件系统配置为 LocalFileSystem，不支持。您必须设置一个分布式文件系统，例如 HDFS 作为默认值。

虽然 Kudu 是一个独立的存储系统并且不依赖于 HDFS，但 Impala 似乎仍然需要一个非本地的默认 FS，即使与 Kudu 一起使用也是如此。Impala_Kudu文档明确列出了以下要求：

在安装 Impala_Kudu 之前，您必须已经为 HDFS（虽然 Kudu 不使用它）、Hive Metastore（Impala 存储其元数据的地方）和 Kudu 安装和配置了服务。

我什至可以想象，除了让 Impala 开心之外，可能真的不需要 HDFS，但这只是我的猜测。更新：发现IMPALA-1850证实了我的怀疑，即 Impala 不再需要 HDFS，但这不仅仅是必须删除的单个检查。

于 2016-09-13T15:14:59.370 回答