Shulou(Shulou.com)06/03 Report--

Warm Tip: to see the high-definition no-code picture, please open it with your mobile phone and click the picture to enlarge.

1. Overview

This document mainly describes the process of deploying CDH5.12.1 Enterprise Edition in CentOS6.5 operating system in offline environment. This installation document is divided into four steps:

1. Preparation (including hostname, turn off firewall, turn off SELinux, clock synchronization, etc.)

two。 Install Cloudera Manager Server

3. Install CDH cluster

4. Cluster integrity check (including whether HDFS file system, MapReduce, Hive and other services can run properly)

This document focuses on the installation of Cloudera Manager and CDH, based on the following assumptions:

1. Operating system version: CentOS6.5

2.MySQL version: 5.1.73

3.CM version: CM 5.12.1

4.CDH version: CDH 5.12.1

5. Deploy the cluster with root

6. You have downloaded the installation packages for CDH and CM (CDH is installed using the parcels package)

two。 Preparation in advance

2.1hostname and hosts configuration

Nodes in the cluster can communicate with each other using static IP addresses. The IP address and hostname are configured through / etc/hosts, and the hostname / etc/hostname is configured (it is recommended that hostname be configured using the FQDN full domain name).

Take the server (172.31.6.148) as an example:

Hostname configuration

Modify the / etc/sysconfig/network file:

[root@ip-172-31-6-148~] # vim / etc/sysconfig/network

NETWORKING=yes

NETWORKING_IPV6=no

HOSTNAME=ip-172-31-6-148.fayson.com

Note: the server needs to be restarted after modifying the hostname.

Check whether the hostname has been modified successfully:

[root@ip-172-31-6-148~] # hostname

Ip-172-31-6-148.fayson.com

[root@ip-172-31-6-148a] #

Hosts configuration

/ etc/hosts file is as follows:

[root@ip-172-31-6-148~] # more / etc/hosts

127.0.0.1 localhost.localdomain localhost

:: 1 localhost6.localdomain6 localhost6

172.31.6.148 ip-172-31-6-148.fayson.com

172.31.5.190 ip-172-31-5-190.fayson.com

172.31.10.118 ip-172-31-10-118.fayson.com

172.31.9.33 ip-172-31-9-33.fayson.com

[root@ip-172-31-6-148a] #

For the above two steps, configure other nodes in the cluster accordingly.

2.2 disable SELinux

Execute the sudo setenforce 0 command on all nodes

[root@ip-172-31-6-148~] # sudo setenforce 0

Modify the / etc/selinux/config file of all nodes in the cluster, as follows:

[root@ip-172-31-6-148~] # vim / etc/selinux/config

This file controls the state ofSELinux on the system.SELINUX= can take one of these three values:enforcing-SELinux security policyis enforced.permissive-SELinux printswarnings instead of enforcing.disabled-No SELinux policy isloaded.

SELINUX=disabled

SELINUXTYPE= can take one of these twovalues:targeted-Targeted processes areprotected,mls-Multi Level Securityprotection.

SELINUXTYPE=targeted

2.3 turn off the firewall

Do the following on all nodes in the cluster and permanently turn off the firewall

[root@ip-172-31-6-148~] # service iptables stop

Iptables: Setting chains to policy ACCEPT: filter [OK]

Iptables: Flushing firewall rules: [OK]

Iptables: Unloading modules: [OK]

[root@ip-172-31-6-148c] # chkconfig iptables off

[root@ip-172-31-6-148a] #

2.4 configure the operating system local yum source

Mount the operating system iso file

[root@ip-172-31-6-148~] # mkdir / mnt/iso

[root@ip-172-31-6-148] # mount-o loop CentOS-6.5-x86_64-minimal.iso/mnt/iso/

[root@ip-172-31-6-148c] # df-h

Filesystem Size UsedAvail Use% Mounted on

/ dev/xvde 99G 3.4G 91G 4% /

Tmpfs 7.4G 0 7.4G 0%/dev/shm

/ root/CentOS-6.5-x86_64-minimal.iso 398M 398M 0100% / mnt/iso

[root@ip-172-31-6-148a] #

Configure the operating system repo

[root@ip-172-31-6-148~] # vim / etc/yum.repos.d/os.repo

Localrepo

Name=CentOS6.5

Baseurl= file:///mnt/iso

Gpgcheck=false

Enabled=true

Check to see if there is a new localrepo in the yum source list

[root@ip-172-31-6-148~] # yum repolist

Loaded plugins: fastestmirror, presto

Loading mirror speeds from cached hostfile

* base: mirror.0x.sg

* extras: mirror.0x.sg

* updates: mirror.0x.sg

Localrepo | 3.6 kB 0015 00...

Localrepo/primary_db | 492kB 00:00...

Repo id reponame status

Base CentOS-6-Base 6706

Cloudera-manager Cloudera Manager, Version 5.12.0 7

Cmrepo cm_repo 7

Extras CentOS-6-Extras 45

Localrepo CentOS6.5 248

Updates CentOS-6-Updates 589

Repolist: 7602

[root@ip-172-31-6-148a] #

2.5 install the http service

Install the http service using yum

Install the http service on one of the nodes of the cluster and execute the following command:

[root@ip-172-31-6-148~] # yum-y install httpd

The installation is successful as shown in the figure above.

Add the httpd service to the system self-startup service and set up boot

[root@ip-172-31-6-148] # chkconfig-- add httpd

[root@ip-172-31-6-148c] # chkconfig httpd on

[root@ip-172-31-6-148] # chkconfig-- list | grep httpd

Httpd 0:off 1:off 2:on 3:on 4:on 5:on 6:off

[root@ip-172-31-6-148a] #

Start the http service

[root@ip-172-31-6-148~] # service httpd start

Starting httpd: [OK]

2.6 redo operating system yum source

After installing the httpd service, re-create the yum source of the operating system, using http, as follows:

Create a centos6.5 directory under the / var/www/html directory

_ root@ip-172-31-6-148_html# mkdir centos6.5

[root@ip-172-31-6-148html] # ll

Total 4

Drwxr-xr-x 2 rootroot 4096 Sep 4 16:04 centos6.5

[root@ip-172-31-6-148html] #

Copy all files in / mnt/iso directory to / var/www/html/centos6.5 directory

_ root@ip-172-31-6-148_html# scp-r / mnt/iso/*/var/www/html/centos6.5/

Modify / etc/yum.repo.d/os.repo configuration

[root@ip-172-31-6-148~] # vim / etc/yum.repos.d/os.repo

Localrepo

Name=CentOS6.5

Baseurl= http://ip-172-31-6-148.fayson.com/centos6.5

Gpgcheck=false

Enabled=true

Check whether the Yum source is configured properly

Synchronize the / etc/yum.repo.d/os.repo configuration file to the / etc/yum.repo.d/ directory of all nodes in the cluster

2.7 Cluster clock synchronization

Install ntp service on all servers in the cluster for clock synchronization in the cluster. Select ip-172-31-6-148.fayson.com server as the local NTP server here, and other nodes in the cluster keep synchronized with it. The configuration is as follows:

Install the ntp service on all nodes in the cluster with the following command

[root@ip-172-31-6-148~] # yum-y install ntp

As shown in the figure above, the installation is successful.

Add ntpd to the system self-startup service and set up boot

Do the following on all nodes:

[root@ip-172-31-6-148] # chkconfig-- add ntpd

[root@ip-172-31-6-148c] # chkconfig ntpd on

Configure synchronization with yourself on ip-172-31-6-148.fayson.com

[root@ip-172-31-6-148~] # vim / etc/ntp.conf

...

Use public servers from thepool.ntp.org project.Please consider joining thepool (http://www.pool.ntp.org/join.html).

# server 0.centos.pool.ntp.org iburst

# server 1.centos.pool.ntp.org iburst

# server 2.centos.pool.ntp.org iburst

# server 3.centos.pool.ntp.org iburst

Server 127.127.1.0 # local clock

Fudge 127.127.1.0 stratum 10

The other nodes of the cluster are configured as follows

[root@ip-172-31-5-190] # vim / etc/ntp.conf

...

Use public servers from thepool.ntp.org project.Please consider joining thepool (http://www.pool.ntp.org/join.html).

# server 0.centos.pool.ntp.org iburst

# server 1.centos.pool.ntp.org iburst

# server 2.centos.pool.ntp.org iburst

# server 3.centos.pool.ntp.org iburst

Server 172.31.6.148 iburst

Restart the ntpd services of all nodes in the cluster

[root@ip-172-31-6-148~] # service ntpd restart

Shutting down ntpd: [OK]

Starting ntpd: [OK]

[root@ip-172-31-6-148a] #

Verify clock synchronization and execute the ntpq-p command on all nodes

[root@ip-172-31-6-148C] # ntpq-p

Remote refid stt when poll reach delay offset jitter

=

* LOCAL (0) .LOCL. 10 l 15 64 7 0.000 0.000 0.001

[root@ip-172-31-6-14814] # ssh-I fayson.pem.txtip-172-31-5-190.fayson.com "ntpq-p"

Remote refid st t when pollreach delay offset jitter

=

* ip-172-31-6-148 LOCAL (0) 11 u 68 128 377 0.274 1.005 0.243

[root@ip-172-31-6-14814] # ssh-I fayson.pem.txtip-172-31-10-118.fayson.com "ntpq-p"

Remote refid stt when poll reach delay offset jitter

=

* ip-172-31-6-148 LOCAL (0) 11 u 75 128 377 0.285 1.214 0.213

[root@ip-172-31-6-148C] # ssh-I fayson.pem.txt ip-172-31-9-33.fayson.com "ntpq-p"

Remote refid stt when poll reach delay offset jitter

=

* ip-172-31-6-148 LOCAL (0) 11 u 1 64 367 0.294-9.249 1.511

[root@ip-172-31-6-148a] #

Note: in the marking part, the "*" display indicates that the synchronization is successful.

2.8Install MySQL

Install MySQL

[root@ip-172-31-6-148~] # yum-y install mysql mysql-server

The screenshot above indicates that MySQL is installed successfully.

Add mysqld to the system self-startup service and set up boot

[root@ip-172-31-6-148] # chkconfig-- add mysqld

[root@ip-172-31-6-148c] # chkconfig mysqld on

Start and configure Mysql

[root@ip-172-31-6-148~] # service mysqld start

...

[OK]

Starting mysqld: [OK]

Initialize MySQL

[root@ip-172-31-6-148~] # mysql_secure_installation

NOTE: RUNNING ALL PARTS OF THIS SCRIPT IS RECOMMENDED FOR ALL MySQL

SERVERS IN PRODUCTIONUSE! PLEASE READ EACH STEP CAREFULLY!

In order to log into MySQL to secure it, we'll need the current

Password for the root user. If you've just installed MySQL, and

You haven't set the root password yet, the passwordwill be blank

So you should just press enter here.

Enter current password for root (enter for none):

OK, successfully used password, moving on...

Setting the root password ensures that nobody can log into the MySQL

Root user without the proper authorisation.

Set root password? Y/n y

New password:

Re-enter new password:

Password updated successfully!

Reloading privilege tables..

... Success!

By default, a MySQL installation has an anonymous user, allowing anyone

To log into MySQL without having to have a user account created for

Them. This is intended only for testing,and to make the installation

Go a bit smoother. You should removethem before moving into a

Production environment.

Remove anonymous users? Y/n y

... Success!

Normally, root should only be allowed to connect from 'localhost'. This

Ensures that someone cannot guess at the root password from the network.

Disallow root login remotely? Y/n n

... Skipping.

By default, MySQL comes with a database named 'test' that anyone can

Access. This is also intended only fortesting, and should be removed

Before moving into a production environment.

Remove test database and access to it? Y/n y

Dropping test database...

... Success!Removing privileges on test database...

... Success!

Reloading the privilege tables will ensure that all changes made so far

Will take effect immediately.

Reload privilege tables now? Y/n y

... Success!

Cleaning up...

All done! If you've completed all of the above steps, your MySQL

Installation should now be secure.

Thanks for usingMySQL!

[root@ip-172-31-6-148a] #

Note: the red section is the input, and "Thanks for using MySQL!" appears. Indicates that initialization is successful.

Create databases for CM and CDH services

Database building statement:

Create database metastore default character set utf8

CREATE USER 'hive'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON metastore. * TO 'hive'@'%'

FLUSH PRIVILEGES

Create database cm default character set utf8

CREATE USER 'cm'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON cm. * TO 'cm'@'%'

FLUSH PRIVILEGES

Create database am default character set utf8

CREATE USER 'am'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON am. * TO 'am'@'%'

FLUSH PRIVILEGES

Create database rm default character set utf8

CREATE USER 'rm'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON rm. * TO 'rm'@'%'

FLUSH PRIVILEGES

Create database hue default character set utf8

CREATE USER 'hue'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON hue. * TO 'hue'@'%'

FLUSH PRIVILEGES

Create database oozie default character set utf8

CREATE USER 'oozie'@'%' IDENTIFIED BY' password'

GRANT ALL PRIVILEGES ON oozie. * TO 'oozie'@'%'

FLUSH PRIVILEGES

The command line operations are as follows:

[root@ip-172-31-6-148C] # mysql-uroot-p

Enter password:

...

Mysql > create database metastore default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'hive'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON metastore. * TO 'hive'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql >

Mysql > create databasecm default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'cm'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON cm. * TO 'cm'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql_ > create database_am default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'am'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON am. * TO 'am'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql >

Mysql > create databaserm default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'rm'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON rm. * TO 'rm'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql >

Mysql > create databasehue default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'hue'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON hue. * TO 'hue'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql >

Mysql > create databaseoozie default character set utf8

Query OK, 1 row affected (0.00 sec)

Mysql > CREATE USER 'oozie'@'%' IDENTIFIEDBY' password'

Query OK, 0 rows affected (0.00 sec)

Mysql > GRANT ALL PRIVILEGES ON oozie. * TO 'oozie'@'%'

Query OK, 0 rows affected (0.00 sec)

Mysql > FLUSH PRIVILEGES

Query OK, 0 rows affected (0.00 sec)

Mysql >

Install the jdbc driver

[root@ip-172-31-6-148~] # mkdir-p / usr/share/java

[root@ip-172-31-6-148c] # mv mysql-connector-java-5.1.34.jar/usr/share/java/

[root@ip-172-31-6-148] # cd / usr/share/java/

[root@ip-172-31-6-148java] # ln-s mysql-connector-java-5.1.34.jar mysql-connector-java.jar

[root@ip-172-31-6-148java] # ll

Total 940

-rwxr-xr-x. 1 root root 960372 Aug 30 15:16 mysql-connector-java-5.1.34.jar

Lrwxrwxrwx 1root root 31 Sep 4 16:32 mysql-connector-java.jar-> mysql-connector-java-5.1.34.jar

[root@ip-172-31-6-148java] #

3.Cloudera Manager installation

3.1Configuring CM local repo source

Download address of CM5.12.1:

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/cloudera-manager-agent-5.12.1-1.cm5121.p0.6.el6.x86\_64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/cloudera-manager-daemons-5.12.1-1.cm5121.p0.6.el6.x86\_64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/cloudera-manager-server-5.12.1-1.cm5121.p0.6.el6.x86\_64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/cloudera-manager-server-db-2-5.12.1-1.cm5121.p0.6.el6.x86\_64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/enterprise-debuginfo-5.12.1-1.cm5121.p0.6.el6.x86\_64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/jdk-6u31-linux-amd64.rpm

Http://archive.cloudera.com/cm5/redhat/6/x86\_64/cm/5.12.1/RPMS/x86\_64/oracle-j2sdk1.7-1.7.0+update67-1.x86\_64.rpm

Download the above 7 files to the server's / var/www/html/cm5.12.1 directory

[root@ip-172-31-6-148~] # mkdir-p / var/www/html/cm5.12.1

[root@ip-172-31-6-148] # cd / var/www/html/cm5.12.1/

[root@ip-172-31-6-148cm5.12.1] # ll

Total 942088

-rw-r--r-- 1 rootroot 9676820 Aug 30 14:45cloudera-manager-agent-5.12.1-1.cm5121.p0.6.el6.x86_64.rpm

-rw-r--r-- 1 rootroot 709818804 Aug 30 14:45 cloudera-manager-daemons-5.12.1-1.cm5121.p0.6.el6.x86_64.rpm

-rw-r--r-- 1 rootroot 8692 Aug 30 14:45cloudera-manager-server-5.12.1-1.cm5121.p0.6.el6.x86_64.rpm

-rw-r--r-- 1 rootroot 10600 Aug 30 14:45cloudera-manager-server-db-2-5.12.1-1.cm5121.p0.6.el6.x86_64.rpm

-rw-r--r-- 1 rootroot 31918952 Aug 30 14:45enterprise-debuginfo-5.12.1-1.cm5121.p0.6.el6.x86_64.rpm

-rw-r--r-- 1 rootroot 71204325 Aug 30 14:45jdk-6u31-linux-amd64.rpm

-rw-r--r-- 1 rootroot 142039186 Aug 30 14:45 oracle-j2sdk1.7-1.7.0+update67-1.x86_64.rpm

[root@ip-172-31-6-148cm5.12.1] #

Execute the command in the / var/www/html/cm5.12.1 directory

[root@ip-172-31-6-148cm5.12.1] # pwd

/ var/www/html/cm5.12.1

[root@ip-172-31-6-148cm5.12.1] # createrepo.

Spawning worker 0 with 7 pkgs

Workers Finished

Gathering worker results

Saving Primary metadata

Saving file lists metadata

Saving other metadata

Generating sqlite DBs

Sqlite DBs complete

[root@ip-172-31-6-148cm5.12.1] #

Confirm that http can be accessed properly

Add the cm.repo file to the / etc/yum.repo.d/ directory as follows

[root@ip-172-31-6-148~] # vim / etc/yum.repos.d/cm.repo

Cmrepo

Name=CM5.12.1

Baseurl= http://ip-172-31-6-148.fayson.com/cm5.12.1

Gpgcheck=false

Enabled=true

Verify that the CM source is configured successfully

[root@ip-172-31-6-148~] # yum repolist

...

Cmrepo CM5.12.1 7

Localrepo CentOS6.5 248

Verify installation of JDK

[root@ip-172-31-6-148C] # yum-y install oracle-j2sdk1.7-1.7.0+update67-1

3.2 configure http to access the CDH Parcel package

Download address of CDH5.12.1:

Http://archive.cloudera.com/cdh6/parcels/5.12.1/CDH-5.12.1-1.cdh6.12.1.p0.3-el6.parcel

Http://archive.cloudera.com/cdh6/parcels/5.12.1/CDH-5.12.1-1.cdh6.12.1.p0.3-el6.parcel.sha1

Http://archive.cloudera.com/cdh6/parcels/5.12.1/manifest.json

Download the above three files to the / var/www/html/cdh6.12.1 directory

[root@ip-172-31-6-148~] # mkdir-p / var/www/html/cdh6.12.1

[root@ip-172-31-6-148] # cd / var/www/html/cdh6.12.1/

[root@ip-172-31-6-148cdh6.12.1] # ll

Total 1582508

-rw-r--r-- 1 rootroot 1620405492 Aug 30 19:09 CDH-5.12.1-1.cdh6.12.1.p0.3-el6.parcel

-rw-r--r-- 1 rootroot 41 Aug 30 19:09 CDH-5.12.1-1.cdh6.12.1.p0.3-el6.parcel.sha1

-rw-r--r-- 1 rootroot 72312 Aug 30 19:11 manifest.json

[root@ip-172-31-6-148cdh6.12.1] #

Confirm that http can be accessed properly

3. 3 install Cloudera Manager Server

Install ClouderaManager Server through yum

[root@ip-172-31-6-148C] # yum-y installcloudera-manager-server

The installation is successful as shown in the figure above.

Initialize the CM database

[root@ip-172-31-6-148] # / usr/share/cmf/schema/scm_prepare_database.sh mysql cm cm password

JAVA_HOME=/usr/java/jdk1.7.0_67-cloudera

Verifying that we can write to / etc/cloudera-scm-server

Creating SCM configuration file in / etc/cloudera-scm-server

Executing: / usr/java/jdk1.7.0_67-cloudera/bin/java-cp/usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/share/cmf/schema/../lib/*com.cloudera.enterprise.dbutil.DbCommandExecutor/etc/cloudera-scm-server/db.properties com.cloudera.cmf.db.

[main] DbCommandExecutor INFO Successfully connected to database.

All done, your SCM database is configured correctly!

[root@ip-172-31-6-148a] #

Start ClouderaManager Server

[root@ip-172-31-6-148~] # service cloudera-scm-server start

Starting cloudera-scm-server: [OK]

[root@ip-172-31-6-148a] #

Check if the port is listening

[root@ip-172-31-6-148~] # netstat-lnpt | grep 7180

Tcp 0 0 0.0.0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0. 0

[root@ip-172-31-6-148a] #

Access the CM console through http:// 52.221.194.202:7180/cmf/login

4.CDH installation

4.1CDH Cluster installation Wizard

1.admin/admin logs in to CM

two。 Agree to the license agreement and click continue

3. Select 60 for trial and click to continue

4. Click "continue"

5. Enter the ip or name of the host, click search to find the host, and click continue

6. Click "continue"

7. Using the parcel option, click "more options", click "-" to delete all other addresses, enter

Http:// ip-172-31-6-148.fayson.com/cdh6.12.1/ Click "Save changes"

8. Select a custom repository and enter the http address of cm

9. Click "continue" to proceed to the next step to install jdk

10. Click "continue" to proceed to the next step, default multi-user mode

11. Click "continue" to proceed to the next step to configure the ssh account password

twelve。 Click "continue" to proceed to the next step, install Cloudera Manager related to each node

13. Click "continue" to proceed to the next step to install cdh to each node

14. Click "continue" to proceed to the next host check to ensure that all check items are passed.

Click finish to enter the service installation wizard.

4.2 Cluster setup installation Wizard

1. Select the services to be installed

Custom services are used here, as shown in the following figure

two。 Click "continue" to enter the cluster role assignment

HDFS role assignment:

Hive role assignment:

Cloudera Manager Service role assignment:

Spark role assignment: (Spark on Yarn so there are no master and worker roles for spark)

Yarn role assignment:

Zookeeper role assignment: (at least 3 Server)

3. When the role assignment is complete, click "continue" to proceed to the next step, test the database connection.

4. If the test is successful, click "continue" to enter the directory settings. Use the default default directory here and modify the directory according to the actual situation.

5. Click "continue" and wait for the service to start successfully

6. Click "continue" to show that the cluster installation is successful

7. Enter the home management interface after successful installation

Drunken whips are famous horses, and teenagers are so pompous! Lingnan Huan Xisha, under the vomiting liquor store! The best friend refuses to let go, the flower of data play!

Warm Tip: to see the high-definition no-code picture, please open it with your mobile phone and click the picture to enlarge.

Welcome to follow Hadoop practice, the first time, share more Hadoop practical information, like please follow and share.

Original article, welcome to reprint, reprint please indicate: reproduced from the official account of Wechat Hadoop

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.