MyException - 我的异常网
当前位置:我的异常网» 云计算 » cloudera-manager-el5-cm5.三.2_x86_64 installatio

cloudera-manager-el5-cm5.三.2_x86_64 installation instruction

www.MyException.Cn  网友分享于:2018-05-29  浏览:0次
cloudera-manager-el5-cm5.3.2_x86_64 installation instruction
Step 1:install mysql-5.5 and config
[ccms@jabtc1337 CDH5]$ cd /usr/local/clo/ven/CDH5
[ccms@jabtc1337 CDH5]$ tar -zxvf mysql-5.5.42-linux2.6-x86_64.tar.gz
[ccms@jabtc1337 CDH5]$ cd mysql-5.5.42-linux2.6-x86_64
[ccms@jabtc1337 CDH5]$ cd mysql-5.5.42-linux2.6-x86_64/support-files/
[ccms@jabtc1337 support-files]$ cp my-small.cnf my.cnf
[ccms@jabtc1337 support-files]$ vi my.cnf
add following setting for INNODB:
[mysqld]
character-set-server=utf8
default-storage-engine=INNODB

# Uncomment the following if you are using InnoDB tables
innodb_data_home_dir = /usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/data
innodb_data_file_path = ibdata1:10M:autoextend
innodb_log_group_home_dir = /usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/data
# You can set .._buffer_pool_size up to 50 - 80 %
# of RAM but beware of setting memory usage too high
innodb_buffer_pool_size = 16M
innodb_additional_mem_pool_size = 2M
# Set .._log_file_size to 25 % of buffer pool size
innodb_log_file_size = 5M
innodb_log_buffer_size = 8M
innodb_flush_log_at_trx_commit = 1
innodb_lock_wait_timeout = 50

[ccms@jabtc1337 mysql-5.5.42-linux2.6-x86_64]$./scripts/mysql_install_db --defaults-file=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/support-files/my.cnf --basedir=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64 --datadir=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/data --user=ccms
[ccms@jabtc1337 mysql-5.5.42-linux2.6-x86_64]$ ./bin/mysqld --defaults-file=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/support-files/my.cnf --basedir=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64 --datadir=/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/data
[ccms@jabtc1337 mysql-5.5.42-linux2.6-x86_64]$/usr/local/clo/ven/CDH5/mysql-5.5.42-linux2.6-x86_64/bin/mysqladmin -u root password '123456'

[ccms@jabtc1337 mysql-5.5.42-linux2.6-x86_64]$ ./bin/mysql -uroot -p123456
#hive
mysql> create database hive DEFAULT CHARSET utf8 COLLATE utf8_general_ci;
Query OK, 1 row affected (0.00 sec)

#activity monitor
mysql> create database amon DEFAULT CHARSET utf8 COLLATE utf8_general_ci;
Query OK, 1 row affected (0.01 sec)

mysql> grant all privileges on *.* to 'root'@'localhost' identified by '123456' with grant option;
Query OK, 0 rows affected (0.00 sec)

#this user scm is for  cloudera manager
mysql> grant all privileges on *.* to 'scm'@'localhost' identified by 'scm' with grant option;
Query OK, 0 rows affected (0.00 sec)

mysql> flush privileges;
Query OK, 0 rows affected (0.00 sec)

#install cloudera-manager-el5-cm5.3.2
[ccms@jabtc1337 CDH5]$ cd /usr/local/clo/ven/CDH5
[ccms@jabtc1337 CDH5]$ tar -zxvf cloudera-manager-el5-cm5.3.2_x86_64.tar.gz

#cp mysql jdbc driver to cmf lib
[ccms@jabtc1337 CDH5]$ cp mysql-connector-java-5.1.34-bin.jar /usr/local/clo/ven/CDH5/cm-5.3.2/share/cmf/lib

#cp CDH-5.3.2-1.cdh5.3.2.p0.10-el5.parcel for deploy
[ccms@jabtc1337 CDH5]$ cp /usr/local/clo/ven/CDH5/CDH-5.3.2-1.cdh5.3.2.p0.10-el5.parcel /usr/local/clo/ven/CDH5/cloudera/parcel-repo/
[ccms@jabtc1337 CDH5]$ cp /usr/local/clo/ven/CDH5/CDH-5.3.2-1.cdh5.3.2.p0.10-el5.parcel.sha /usr/local/clo/ven/CDH5/cloudera/parcel-repo/

#initial cm-5.3.2 database
[ccms@jabtc1337 CDH5]$ /usr/local/clo/ven/CDH5/cm-5.3.2/share/cmf/schema/scm_prepare_database.sh mysql cm -hlocalhost:3306 -uroot -p123456 --scm-host localhost scm scm scm
JAVA_HOME=/opt/jdk1.6.0_23
Verifying that we can write to /usr/local/clo/ven/CDH5/cm-5.3.2/etc/cloudera-scm-server
Creating SCM configuration file in /usr/local/clo/ven/CDH5/cm-5.3.2/etc/cloudera-scm-server
id: cloudera-scm: No such user
Executing:  /opt/jdk1.6.0_23/bin/java -cp /usr/share/java/mysql-connector-java.jar:/usr/share/java/oracle-connector-java.jar:/usr/local/clo/ven/CDH5/cm-5.3.2/share/cmf/schema/../lib/* com.cloudera.enterprise.dbutil.DbCommandExecutor /usr/local/clo/ven/CDH5/cm-5.3.2/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!

#start cloudera-scm-server with root, it need about 10 minitues to start
[ccms@jabtc1337 CDH5]$ /usr/local/clo/ven/CDH5/cm-5.3.2/etc/init.d/cloudera-scm-server start
Starting cloudera-scm-server:                              [  OK  ]

[ccms@jabtc1337 CDH5]$ tail -f /usr/local/clo/ven/CDH5/cm-5.3.2/log/cloudera-scm-server/cloudera-scm-server.log
......
2015-03-12 02:04:15,998 INFO WebServerImpl:org.mortbay.log: Started SelectChannelConnector@0.0.0.0:7180
2015-03-12 02:04:15,998 INFO WebServerImpl:com.cloudera.server.cmf.WebServerImpl: Started Jetty server.

#login cloudera manager console with following url, with user/password as admin/admin
http://localhost:7180/cmf/login

#start cloudera-scm-agent with root
[root@jabtc1337 cm-5.3.2]$ /usr/local/clo/ven/CDH5/cm-5.3.2/etc/init.d/cloudera-scm-agent start
Starting cloudera-scm-agent:                               [  OK  ]

#update python 2.4 to 2.7180
#update jdk 1.6.0_23 to 1.6.0_31

文章评论

相关解决方案
  • 暂无相关解决方案
软件开发程序错误异常ExceptionCopyright © 2009-2015 MyException 版权所有