Reply
Explorer
Posts: 28
Registered: ‎03-25-2017

Cloudera 5.11.0 Cluster installation

Hi, 

I am working as Cloudera Hadoop administration since 2 years and have done multiples of installation and upgradation so far. Last successful cluster installation I have done was 5.7.2. As 5.11 includes kudu with security, I am trying to install 5.11 cluster on new set of servers  with centos installed  to  explore kudu and integrate existing system with it. I have downloaded tarbal package of cm and cdh and installed it on every system .After installing cm server and agents and along with cdh and open cloudera manager in browser after selecting the nodes ,it ask  below 

  1. Package or parcels 
  2. Version to install
  3. Repository location And once I gave local repository location and proceed for installation. It again install everything which flood the root mount and fails installation. 

After increasing the root mount size, it's installting every component and restarting the cloudera agent but restart fails and complete installation get roll back. 

 

So  my questions are ,

  1. why does it requires repository location when I select packages.
  2. Why it try to install again all components when I have already installed the required one.
  3. Why it restart cloudera agent at the end and then it fails because of some permission issue related to cloudera-scm user.

Please help me to resolve this

Explorer
Posts: 28
Registered: ‎03-25-2017

Re: Cloudera 5.11.0 Cluster installation

Can anyone kindly help me out  for this?

Explorer
Posts: 28
Registered: ‎03-25-2017

Re: Cloudera 5.11.0 Cluster installation

Is there no one who can help to explain above?
Champion
Posts: 410
Registered: ‎05-16-2016

Re: Cloudera 5.11.0 Cluster installation

  1. Why it restart cloudera agent at the end and then it fails because of some permission issue related to cloudera-scm user.

Could you provide us the logs for more insight as to why cloudera manager agent fails 

 

I belive you are following PATH B installation steps . ? correct me if I am wrong 

what Version of  Centos / kernel 

 

 

 

Explorer
Posts: 28
Registered: ‎03-25-2017

Re: Cloudera 5.11.0 Cluster installation

Hi,

Thanks. I resolved those issue I still want to know the answer of my
questions.

Regards
Sidharth
Explorer
Posts: 28
Registered: ‎03-25-2017

Re: Cloudera 5.11.0 Cluster installation

my questions are ,

  1. why does it requires repository location when I select packages.
  2. Why it try to install again all components when I have already installed the required one.
Posts: 552
Topics: 3
Kudos: 77
Solutions: 49
Registered: ‎08-16-2016

Re: Cloudera 5.11.0 Cluster installation

There are three sources of installation: tarballs, packages, and parcels.

CM only supports packages and parcels for CDH services.

You can use tarballs to install everything from Java to HDFS, but then CM isn't aware and can't manage them.

So to specifically answer your questions.
1. It needs to know the repository location of the packages and pacels, as these are the only supported options for CM to install CDH services.
2. CM needs to complete the installation so that it is aware of the installation of the CDH services.
3. I can't be certain but it is likely but typically when CM installs the agents it has them run as the 'cloudera-scm' user (same for CM and CMS as well). It is possible to install the CM agents using tarballs or packages and have it run as another user or root, but then you need to skip installing them in CM. This can be done by switching tabs on the screen for adding agents. I don't recall the labeling but it starts with the a screen where you can enter the hostnames or ips of the agents. There should be a tab to see existing agents. If your agents are reporting to CM correctly they will be here, you can selected them, and include them in the CDH services installation.

https://www.cloudera.com/documentation/enterprise/5-8-x/topics/cm_ig_install_path_b.html
Highlighted
Champion
Posts: 410
Registered: ‎05-16-2016

Re: Cloudera 5.11.0 Cluster installation

Just curious to know what did you do 

I resolved those issue
Announcements