新手园地& & & 硬件问题Linux系统管理Linux网络问题Linux环境编程Linux桌面系统国产LinuxBSD& & & BSD文档中心AIX& & & 新手入门& & & AIX文档中心& & & 资源下载& & & Power高级应用& & & IBM存储AS400Solaris& & & Solaris文档中心HP-UX& & & HP文档中心SCO UNIX& & & SCO文档中心互操作专区IRIXTru64 UNIXMac OS X门户网站运维集群和高可用服务器应用监控和防护虚拟化技术架构设计行业应用和管理服务器及硬件技术& & & 服务器资源下载云计算& & & 云计算文档中心& & & 云计算业界& & & 云计算资源下载存储备份& & & 存储文档中心& & & 存储业界& & & 存储资源下载& & & Symantec技术交流区安全技术网络技术& & & 网络技术文档中心C/C++& & & GUI编程& & & Functional编程内核源码& & & 内核问题移动开发& & & 移动开发技术资料ShellPerlJava& & & Java文档中心PHP& & & php文档中心Python& & & Python文档中心RubyCPU与编译器嵌入式开发驱动开发Web开发VoIP开发技术MySQL& & & MySQL文档中心SybaseOraclePostgreSQLDB2Informix数据仓库与数据挖掘NoSQL技术IT业界新闻与评论IT职业生涯& & & 猎头招聘IT图书与评论& & & CU技术图书大系& & & Linux书友会二手交易下载共享Linux文档专区IT培训与认证& & & 培训交流& & & 认证培训清茶斋投资理财运动地带快乐数码摄影& & & 摄影器材& & & 摄影比赛专区IT爱车族旅游天下站务交流版主会议室博客SNS站务交流区CU活动专区& & & Power活动专区& & & 拍卖交流区频道交流区
空间积分0 信誉积分88 UID阅读权限10积分28帖子精华可用积分28 专家积分0 在线时间41 小时注册时间最后登录
白手起家, 积分 28, 距离下一级还需 172 积分
帖子主题精华可用积分28 专家积分0 在线时间41 小时注册时间最后登录
论坛徽章:0
各位大神，请指点下：
我在安装cloudera manager 的时候提示Starting cloudera-scm-server: [FAILED]
service cloudera-scm-server start
Starting cloudera-scm-server: [FAILED]
好几次安装的时候出现这个问题，后来manager 安装成功了，但是我手动也无法启动这个服务。我安装的系统是centos6.4
下面是日志
# cat cloudera-scm-server.log
13:59:15,981&&INFO [main:support.ClassPathXmlApplicationContext@456] Refreshing org.springframework.context.support.ClassPathXmlApplicationContext@65b4fad5: startup date [Thu Nov 28 13:59:15 CST 2013]; root of context hierarchy
13:59:16,092&&INFO [mainml.XmlBeanDefinitionReader@315] Loading XML bean definitions from class path resource [webapp/WEB-INF/spring/beanRefFactory.xml]
13:59:16,510&&INFO [main:support.DefaultListableBeanFactory@557] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@739e8329: defining beans [bootstrapContext,rootContext]; root of factory hierarchy
13:59:16,569&&INFO [main:support.GenericApplicationContext@456] Refreshing org.springframework.context.support.GenericApplicationContext@6f878144: startup date [Thu Nov 28 13:59:16 CST 2013]; root of context hierarchy
13:59:16,572&&INFO [main:support.DefaultListableBeanFactory@557] Pre-instantiating singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7ac2b2f6: defining beans [commandLineConfigurationBean,entityManagerFactoryBean,com.cloudera.server.cmf.TrialState,com.cloudera.server.cmf.TrialManager,com.cloudera.cmf.LicenseData$LicenseDataProvider]; root of factory hierarchy
13:59:16,758&&INFO [monMain@94] Reading database properties from /etc/cloudera-scm-server/db.properties
13:59:16,771&&INFO [monMain@127] Statistics not enabled, c3p0 JMX disabled
13:59:17,107&&INFO [main:common.Version@37] HCANN000001: Hibernate Commons Annotations {4.0.1.Final}
13:59:17,123&&INFO [main:hibernate.Version@41] HHH000412: Hibernate Core {4.1.4.Final}
13:59:17,129&&INFO [main:cfg.Environment@239] HHH000206: hibernate.properties not found
13:59:17,132&&INFO [main:cfg.Environment@342] HHH000021: Bytecode provider name : javassist
13:59:17,813&&INFO [main:cfg.Configuration@718] HHH000221: Reading mappings from resource: cmf.hbm.xml
13:59:18,900&&INFO [main:internal.ConnectionProviderInitiator@188] HHH000130: Instantiating explicit connection provider: org.hibernate.service.jdbc.connections.internal.C3P0ConnectionProvider
13:59:18,902&&INFO [main:internal.C3P0ConnectionProvider@128] HHH010002: C3P0 using driver: com.mysql.jdbc.Driver at URL: jdbc:mysql://null/null?useUnicode=true&characterEncoding=UTF-8
13:59:18,903&&INFO [main:internal.C3P0ConnectionProvider@129] HHH000046: Connection properties: {user=, password=****, autocommit=true, release_mode=auto}
13:59:18,903&&INFO [main:internal.C3P0ConnectionProvider@132] HHH000006: Autocommit mode: true
13:59:18,909&&INFO [main:support.DefaultListableBeanFactory@422] Destroying singletons in org.springframework.beans.factory.support.DefaultListableBeanFactory@7ac2b2f6: defining beans [commandLineConfigurationBean,entityManagerFactoryBean,com.cloudera.server.cmf.TrialState,com.cloudera.server.cmf.TrialManager,com.cloudera.cmf.LicenseData$LicenseDataProvider]; root of factory hierarchy
13:59:18,910 ERROR [main:cmf.Main@189] Server failed.
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'com.cloudera.server.cmf.TrialState': Cannot resolve reference to bean 'entityManagerFactoryBean' while setting
nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean threw exceptio nested exception is javax.persistence.PersistenceException: [PersistenceUnit: cmf.server] Unable to build EntityManagerFactory
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:32
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveValueIfNecessary(BeanDefinitionValueResolver.java:106)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.resolveConstructorArguments(ConstructorResolver.java:616)
& && &&&at org.springframework.beans.factory.support.ConstructorResolver.autowireConstructor(ConstructorResolver.java:14
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.autowireConstructor(AbstractAutowireCapableBeanFactory.java:1003)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:907)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:485)
& && &&&at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:456)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:293)
& && &&&at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:222)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:290)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:585)
& && &&&at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:895)
& && &&&at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:425)
& && &&&at com.cloudera.server.cmf.Main.bootstrapSpringContext(Main.java:316)
& && &&&at com.cloudera.server.cmf.Main.&init&(Main.java:199)
& && &&&at com.cloudera.server.cmf.Main.main(Main.java:184)
Caused by: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'entityManagerFactoryBean': FactoryBean threw exceptio nested exception is javax.persistence.PersistenceException: [PersistenceUnit: cmf.server] Unable to build EntityManagerFactory
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.doGetObjectFromFactoryBean(FactoryBeanRegistrySupport.java:149)
& && &&&at org.springframework.beans.factory.support.FactoryBeanRegistrySupport.getObjectFromFactoryBean(FactoryBeanRegistrySupport.java:102)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getObjectForBeanInstance(AbstractBeanFactory.java:1440)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:247)
& && &&&at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:192)
& && &&&at org.springframework.beans.factory.support.BeanDefinitionValueResolver.resolveReference(BeanDefinitionValueResolver.java:322)
& && &&&... 17 more
& |& & |& & |& & |& 
北京皓辰网域网络信息技术有限公司. 版权所有 京ICP证:060528号 北京市公安局海淀分局网监中心备案编号：
广播电视节目制作经营许可证(京) 字第1234号
中国互联网协会会员&&联系我们：
感谢所有关心和支持过ChinaUnix的朋友们
转载本站内容请注明原作者名及出处Download Cloudera Manager 5.1.3
Instructions for Installing Previous Cloudera Manager Versions
To install any previous version of Cloudera Manager 5, you must create a custom repository for the RPM or DEB Files.
See the instructions in&.
The download locations of the 5.0.x RPM or DEB Files are listed in&.
Fixed Issues in Cloudera Manager 5.1.3
Adding and upgrading hosts allows users to skip installing default JDK that ships with Cloudera Manager
Users who are adding or upgrading hosts can choose not to install the JDK that ships with Cloudera Manager.
Improved speed and heap usage when deleting hosts on cluster with long history
Speed and heap usage have been improved when deleting hosts on clusters that have been running for a long time.
When there are multiple clusters, each cluster's topology files and validation for legal topology is limited to hosts in that cluster
When there are multiple clusters, each cluster's topology files and validation for legal topology is limited to hosts in that cluster. Most commands will now fail up front if the cluster's topology is invalid.
The size of the statement cache has been reduced for Oracle databases
For users of Oracle databases, the size of the statement cache has been reduced to help with memory consumption.
Improvements to memory usage of &cluster diagnostics collection& for large clusters.
Memory usage of &cluster diagnostics collection& has been improved for large clusters.
Cloudera Manager 5.1.x System Requirements:
Supported Operating Systems
Cloudera Manager supports the following operating systems:
RHEL-compatible systems
Red Hat Enterprise Linux and CentOS 5.7, 64-bit
Red Hat Enterprise Linux and CentOS 6.2, 64-bit
Red Hat Enterprise Linux and CentOS 6.4, 64-bit
Oracle Enterprise Linux 6.4, 64-bit
Oracle Enterprise Linux 5.6, 64-bit
SLES - SUSE Linux Enterprise Server 11, 64-bit. Service Pack 2 or later is required for CDH 5 and Service Pack 1 or later is required for CDH 4. To use the embedded PostgreSQL database that is installed when you follow , the Updates repository must be active. The
is required on hosts running the Cloudera Manager Agents.
Debian - Debian 7.0 and 7.1, 6.0 (deprecated), 64-bit
Ubuntu - Ubuntu 12.04, 10.04 (deprecated), 64-bit
Debian 6.0 and Ubuntu 10.04 are supported only for CDH 4.
Using the same version of the same operating system on all cluster hosts is strongly recommended.
Supported JDK Versions
Cloudera Manager supports Oracle JDK 7u45 and Oracle JDK 6u31, and will also install them. Additionally, Cloudera Manager supports JDK1.7u25.
Supported Databases
Cloudera Manager requires several databases. The Cloudera Manager Server stores information about configured services, role assignments, configuration history, commands, users, and running processes in a database of its own. You must also specify a database for the Activity Monitor and Reports Manager management services.
The database you choose to use must be configured to support UTF8 character set encoding. The embedded PostgreSQL database that is installed when you follow
automatically provides UTF8 encoding. If you install a custom database, you may need to enable UTF8 encoding. The commands for enabling UTF8 encoding are described in each database's section under .
After installing a database, upgrade to the latest patch version and apply any other appropriate updates. The available updates may be specific to the operating system on which it is installed.
Cloudera Manager and its supporting services can use the following databases:
MySQL - 5.5 and 5.6
Oracle - 11g Release 2
PostgreSQL - 8.1, 8.4, and 9.2
For information about the databases supported by CDH, see
Supported Supported CDH and Other Managed Service Versions
The following versions of CDH and other managed services are supported:& Warning: Cloudera Manager 5 does not support CDH 3 and you cannot upgrade Cloudera Manager 4 to Cloudera Manager 5 if you have a cluster running CDH 3. Therefore, to upgrade CDH 3 clusters to CDH 4 using Cloudera Manager you must use Cloudera Manager 4.
CDH 4 and CDH 5. The latest released versions of CDH 4 and CDH 5 are strongly recommended. For information on CDH 4 requirements, see . For information on CDH 5 requirements, see .
Cloudera Impala 1.2.1 or later with CDH 4.1.0 or later. For information on Cloudera Impala requirements, see Cloudera Impala Requirements.
Cloudera Search - 1.2.0 with CDH 4.6.0. For information on Cloudera Search requirements, see .
Apache Spark 0.90 or later with CDH 4.4.0 or later.
Apache Accumulo 1.4.3 and 1.5.0 with CDH 4.3.0 or later.
Parcels are available for CDH 4.1.3 or later, and for Impala, Search, Spark, and Accumulo.
For more information, see the Cloudera Product Compatibility Matrix.
Resource Requirements
Cloudera Manager requires resources of the following types:
Disk Space
Cloudera Manager Server
5 GB on the partition hosting /var.
500 MB on the partition hosting /usr.
For parcels, the space required depends on the number of parcels you download to the Cloudera Manager Server and distribute to Agent hosts. You can download multiple parcels of the same product, of different versions and builds. If you are managing multiple clusters, there will be only one parcel of a given product/version/build/distribution downloaded on the Cloudera Manager Server—not one per cluster. In the local parcel repository on the Cloudera Manager Server the approximate sizes of the various parcels are as follows:
CDH 4.6 - ~700 MB per parcel, CDH 5 - ~1 GB per parcel
Impala - ~200 MB per parcel
Solr - ~ 400 MB per parcel
Cloudera Management Service - The Host Monitor and Service Monitor databases are stored on the partition hosting /var. Ensure that you have at least 20 GB available on this partition. For further information, see .
Agents - On Agent hosts each unpacked parcel requires about three times the space of the downloaded parcel on the Cloudera Manager Server. By default unpacked parcels are located in /opt/cloudera/parcels.
RAM - 4 GB is appropriate for most cases, and is required when using Oracle databases. 2 GB may be sufficient for non-Oracle deployments involving fewer than 100 hosts. However, if you want to run the Cloudera Manager Server on a machine with 2 GB of RAM, you must tune down its maximum heap size (by modifying -Xmx in /etc/default/cloudera-scm-server). Otherwise the kernel may kill the Server for consuming too much RAM.
Python - Cloudera Manager uses Python. All supported operating systems contain a Python version 2.4 or higher. Cloudera Manager and CDH 4 require at least Python 2.4, but Hue in CDH 5 requires Python 2.6 or 2.7.
Networking and Security Requirements
Cluster hosts must have a working network name resolution system and correctly formatted /etc/hosts file. All cluster hosts must have properly configured forward and reverse host resolution through DNS. The /etc/hosts files must contain consistent information about host names and addresses across all hosts. A properly formatted /etc/hosts should be similar to the following example:
127.0.0.1 localhost.localdomain localhost
192.168.1.1 cluster- cluster-01
192.168.1.2 cluster- cluster-02
192.168.1.3 cluster- cluster-03
In most cases, the Cloudera Manager Server must have SSH access to the cluster hosts when you run the installation or upgrade wizard. You must log in using a root account or an account that has password-less sudo permission. For authentication during the installation and upgrade procedures, you must either enter the password or upload a public and private key pair for the root or sudo user account. If you want to use a public and private key pair, the public key must be installed on the cluster hosts before you use Cloudera Manager.Cloudera Manager uses SSH only during the initial install or upgrade. Once your cluster is set up, you can disable root SSH access or change the root password. Cloudera Manager does not save SSH credentials and all credential information is discarded once the installation is complete. For further information, see .
The Cloudera Manager Agent runs as root so that it can make sure the required directories are created and that processes and files are owned by the appropriate user (for example, the hdfs and mapred users).
No blocking by Security-Enhanced Linux (SELinux).
Disable Ipv6 on all hosts.
No blocking by i make sure port 7180 is open because it is the port used to access Cloudera Manager after installation. Cloudera Manager communicates using specific ports, which must be open. See .
For RedHat and CentOS, make sure the/etc/sysconfig/network file on each system contains the hostname you have just set (or verified) for that system.
Cloudera Manager and CDH use several user accounts and groups to complete their tasks. The set of user accounts and groups varies according to which components you choose to install. Do not delete these accounts or groups and do not modify their permissions and rights. Ensure no existing systems obstruct the functioning of these accounts and groups. For example, if you have scripts that delete user accounts not in a white-list, add these accounts to the list of permitted accounts. Cloudera Manager, CDH, and managed services create and use the following accounts and groups:
&p&JavaScript must be enabled in order to use this site.&/p&&p&Please enable JavaScript in your browser and refresh the page.&/p&
Cloudera Manager Quick Start Guide
This quick start guide describes how to quickly create a new installation of Cloudera Manager 5, CDH 5, and managed services on a cluster of four hosts. The resulting deployment can be used for demonstrations and proof of concept applications, but is not recommended for production.
Requirements
The four hosts in the cluster must satisfy the following requirements:
The hosts must have at least 10 GB RAM
You must have root or password-less sudo access to the hosts
If using root, the hosts must accept the same root password
The hosts must have Internet access to allow the wizard to install software from
Run a supported OS:
RHEL-compatible systems
Red Hat Enterprise Linux and CentOS 5.7, 64-bit
Red Hat Enterprise Linux and CentOS 6.2, 64-bit
Red Hat Enterprise Linux and CentOS 6.4, 64-bit
Oracle Enterprise Linux 6.4, 64-bit
Oracle Enterprise Linux 5.6, 64-bit
SLES - SUSE Linux Enterprise Server 11, 64-bit. Service Pack 2 or later is required. The Updates repository must be active and
is required.
Debian - Debian 7.0 and 7.1, 64-bit
Ubuntu - Ubuntu 12.04, 64-bit
If your environment does not satisfy these requirements, the procedure described in this guide may not be appropriate for you. For information about other Cloudera Manager installation options and requirements, see the .
Download and Run the Cloudera Manager Server Installer
Download the Cloudera Manager installer binary from Cloudera Manager Downloads to the cluster host where you want to install the Cloudera Manager Server.
Under Cloudera Manager 5.x downloads, click Download Cloudera Manager Express Edition.
Optionally register and click Submit or click the Just take me to the download page link.
The cloudera-manager-installer.bin file downloads.
Change cloudera-manager-installer.bin to have executable permission.
$ chmod u+x cloudera-manager-installer.bin
Run the Cloudera Manager Server installer.
$ sudo ./cloudera-manager-installer.bin
Read the Cloudera Manager README and then press Return or Enter to choose Next.
Read the Cloudera Manager Standard License and then press Return or Enter to choose Next. Use the arrow keys and press Return or Enter to choose Yes to confirm you accept the license.
Read the Oracle Binary Code License Agreement and then press Return or Enter to choose Next.
When the installation completes, the complete URL provided for the Cloudera Manager Admin Console, including the port number, which is 7180 by default. Press Return or Enter to choose OK to continue.
Press Return or Enter to choose OK to exit the installer.
On RHEL 5 and CentOS 5, install Python 2.6 or 2.7. Download the appropriate repository rpm packages to the Cloudera Manager Server host and then install Python using yum. For example, use the following commands:
$ su -c 'rpm -Uvh http://download.fedoraproject.org/pub/epel/5/i386/epel-release-5-4.noarch.rpm'
$ yum install python26
& Note: If the installation is interrupted for some reason, you may need to clean up before you can re-run it. See Uninstalling Cloudera Manager and Managed Software in the .
Start the Cloudera Manager Admin Console
Wait several minutes for the Cloudera Manager Server to complete its startup. To observe the startup process you can perform tail -f /var/log/cloudera-scm-server/cloudera-scm-server.log on the Cloudera Manager Server host. If the Cloudera Manager Server does not start, see .
In a web browser, enter http://Server host:7180, where Server host is the fully-qualified domain name or IP address of the host where you installed the Cloudera Manager Server. The login screen for Cloudera Manager Admin Console displays.
Log into Cloudera Manager Admin Console with the credentials: Username: admin Password: admin.
Install and Configure Software Using the Cloudera Manager Wizard
Installing and configuring Cloudera Manager, CDH, and managed service software on the cluster hosts involves the following three main steps.
Choose Cloudera Manager Edition and Specify Hosts
Choose Cloudera Enterprise Data Hub Edition Trial, which does not require a license, but expires after 60 days and cannot be renewed. The trial allows you to create all CDH and managed services supported by Cloudera Manager. Click Continue.
Information is displayed indicating what edition of Cloudera Manager will be installed and the services you can choose from. Click Continue.
Specify the hosts on which to install CDH and managed services. You can specify hostnames and/or IP addresses and ranges, for example: 10.1.1.[1-4] or host[1-3].. You can specify multiple addresses and address ranges by separating them by commas, semicolons, tabs, or blank spaces, or by placing them on separate lines.
Click Search. Cloudera Manager identifies the hosts on your cluster. Verify that the number of hosts shown matches the number of hosts where you want to install services. Deselect host entries that do not exist and deselect the hosts where you do not want to install services. Click Continue. The Select Repository page displays.
Install CDH and Managed Service Software
Keep the default distribution method Use Parcels and the default version of CDH 5.
For the Cloudera Manager Agent, keep the default Matched release for this Cloudera Manager Server. Click Continue twice.
Specify host SSH login properties:
Keep the default login root or enter the user name for an account that has password-less sudo permission.
If you choose to use password authentication, enter and confirm the password.
Click Continue. Cloudera Manager installs the Oracle JDK and the Cloudera Manager Agent packages on each host and starts the Agent.
Click Continue. Cloudera Manager installs CDH. During the parcel installation, progress is indicated for the two phases of the parcel installation process (Download and Distribution) in a separate progress bars. When the Continue button appears at the bottom of the screen, the installation process is completed.
Click Continue. The Host Inspector runs to validate the installation, and provides a summary of what it finds, including all the versions of the installed components. If the validation is successful, click Finish. The Cluster Setup page displays.
Add and Configure Services
Click the All Services radio button to create HDFS, YARN (includes MapReduce 2), ZooKeeper, Oozie, Hive, Hue, Sqoop, HBase, Impala, Solr, Spark, and Key-Value Store Indexer services. Click Continue. The Customize Role Assignments page displays.
Configure the following role assignments:
Click the text field under the HBase Thrift Server role. In the host selection dialog that displays, check the checkbox next to any host and click OK at the bottom right.
Click the text field under the Server role of the ZooKeeper service. In the host selection dialog that displays, uncheck the checkbox next to the host assigned by default (the master host) and check checkboxes next to the remaining three hosts. Click OK at the bottom right.
Click Continue. The Database Setup page displays.
Leave the default setting of Use Embedded Database to have Cloudera Manager create and configure all required databases in an embedded PostgreSQL database. Click Test Connection. When the test completes with a , click Continue. The Review Changes page displays.
Review the configuration changes to be applied. Click Continue. The Command Progress page displays.
The wizard performs 32 steps to configure and starts the services. When the startup completes, click Continue.
A success message displays indicating that the cluster has been successfully started. Click Finish to proceed to the Home page.
Test the Installation
The Home page should look something like this:
On the left side of the screen is a list of services currently running with their status information. All the services should be running with Good Health , however there may be a small number of configuration warnings indicated by a wrench icon and a numbered badge , which you can ignore.
You can click each service to view more detailed information about the service. You can also test your installation by running a MapReduce job or interacting with the cluster with a Hue application.
Running a MapReduce Job
Log into a cluster host.
Run the Hadoop PiEstimator example:
sudo -u hdfs hadoop jar \
/opt/cloudera/parcels/CDH/lib/hadoop-mapreduce/hadoop-mapreduce-examples.jar \
View the result of running the job by selecting the following from the top navigation bar in the Cloudera Manager Admin Console: Clusters & Cluster 1 & YARN (MR2 Included) Applications. You will see an entry like the following:
Testing with Hue
A good way to test the cluster is by running a job. In addition, you can test the cluster by running one of the Hue web applications. Hue is a graphical user interface that allows you to interact with your clusters by running applications that let you browse HDFS, manage a Hive metastore, and run Hive, Impala, and Search queries, Pig scripts, and Oozie workflows.
In the Cloudera Manager Admin Console Home page, click the Hue service.
Click the Hue Web UI tab, which opens Hue in a new window.
Log in with the credentials, username: hdfs, password: hdfs.
Choose an application in the navigation bar at the top of the browser window.
For more information, see the .
This asset is protected
To Download this resource please fill out this registration form
Business Email
First Name
Please select
Analytics / Business Intelligence
Big Data / Architecture
Data Warehouse /Management
Data Science
Infrastructure
Marketing / Sales
Networking
Non technical
Security / Compliance
Job Function
Please select
Administrator
Analyst (Industry/Finance)
Analyst (Technical)
Consultant
Individual contributor
By clicking "Submit" you agree with our .
