search

michalklempa / SEBC

0 stars 0 forks source link

Installation Lab #1

Open michalklempa opened 8 years ago

michalklempa commented 8 years ago

Should I add and mount any non-root block device to each of our cluster nodes? @mikeridley @mfernest

michalklempa commented 8 years ago

MySQL: Plan 2

michalklempa commented 8 years ago

What is

[mysqld]
sql_mode=STRICT_ALL_TABLES

it is required for HUE installation (http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_mysql.html#id_xdr_wvt_g5) will it affect other databases we have put into our mysql?

michalklempa commented 8 years ago

There is cross-dependency in docs: http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_install_path_b.html#id_gzv_zmm_25

Database installation script required in http://www.cloudera.com/documentation/enterprise/latest/topics/cm_ig_installing_configuring_dbs.html#concept_i2r_m3m_hn is not present before the YUM repos and packages are downloaded

mikeridley commented 8 years ago

With respect to the MySQL strict mode, what it means is that MySQL will do additional input validation on things like data type compatibility before allowing data to be written to the database. It will affect all the MySQL databases, but that should be OK. More information on MySQL sql mode is here http://www.mysqlfaqs.net/mysql-client-server-commands/what-is-sql-mode-in-mysql-and-how-can-we-set-it

As far as the documentation issue, I don't see a cross dependency but I see where you are coming from. When the documentation instructs you to install and configure the database server first, they mean configuration from the DBA perspective. Set appropriate kernel parameters, configure storage types, create accounts and databases, etc. Then, once the Cloudera software is installed, you run the Cloudera specific schema population script.

michalklempa commented 8 years ago

After installing, I get CM reporting some configuration alerts. Any suggestions on how to move services to other nodes, or maybe we will ignore this for the scope of this course?

configuration_aletrs

mikeridley commented 8 years ago

One thing you can do is to change the over commit validation threshold. For whatever reason, it's specified as a percentage value and defaults to 0.8 (80%). I often change this to 0.9 (90%). We do want to reserve some memory for the OS and other services to use, and on a relatively small host such as 32 GB of RAM, 80 or 90% is not bad. With production sized hosts with 256 or even 512 GB of RAM, reserving 10% for the OS may be excessive and the value should be increased even further.

Alternatively, you could choose not to worry about it for the purposes of this lab.