On Tue, Jul 16, 2013 at 1:16 PM, Darren Lo wrote:
If you don't have anything running on the cluster yet, then it's probably
easiest to just stop your cluster, delete everything in the data
directories, and delete your cluster, then go through the add cluster
wizard again to set things up how you want.
If you want to move roles around instead, then for each role that supports
decommissioning (such as datanode and regionserver), you can select the
Decommission action one by one. Navigate to the page for that role instance
and select the Decommission command from the Actions menu. If you don't see
the action, then the role can't / doesn't need to be Decommissioned. You
may need to read other documentation for the right way to move roles like
this, such as the NameNode. It's potentially fairly complex, which is why I
recommend setting up your cluster from scratch with the right host
assignments if you can.
If you want to decommission the entire host (which will not affect
Cloudera Manager), you can select the host from the Hosts page and select
the action to decommission everything on the host.
Gateways don't take any resources. They just help keep track of which
hosts should get client configuration when you run the Deploy Client
On Tue, Jul 16, 2013 at 12:56 PM, Tim Washburn wrote:
Thanks for the reply. If I elect to decomm the manager from being a
datanode, regionserver, gateway etc will still operate as my manager? I ask
as the particular machine was selected as the manager based on disk size
and memory. Thinking that the manager's requirements weren't that intensive
when compared to the Namenodes and datanodes. Yes it is small and a POC to
wet the appetite of the business - it may grow up to become a real cluster
some day :--)
Global IT Security
Bio-Rad Laboratories, Inc
From: Darren Lo <email@example.com>
To: Tim Washburn <firstname.lastname@example.org>
Date: 07/16/2013 11:35 AM
Subject: Re: Cluster Setup with Cloudera Manger on with samll
cluster - determining what services/roles for wach member of the cluster.
During initial installation you can pick which hosts have which roles by
clicking Inspect Role Assignments. CM will automatically suggest
assignments, which is what happened on your cluster.
If you want to move roles around, you can use the decommission command to
accomplish this, but there's probably nothing wrong with your current
cluster setup. If you find that you don't have enough RAM on your namenode
host to run your roles well, then you can consider moving some roles off of
that host. Note that I'm assuming this is not a production cluster since
there are so few nodes.
On Mon, Jul 15, 2013 at 3:49 PM, Tim Washburn <*email@example.com*<firstname.lastname@example.org>>
I've just finished setting up a small cluster consisting of the following:
1 single server for the Cloudera manager
2 servers for the primary and secondary namenodes
3 servers for the datanodes.
I used the default templates and allowed CM to determine what each node
would be. For the most part it looks like CM chose the correct items per
member. My question is how to tell if the primary namenode has all the
correct services running? This question also applies to the other nodes as
well. Part of my concern is that the Manager is also a datanode is this
correct? Can I have the Clodera manage be just a manager and not a datanode?
The primary namenode has the the following services running:
The secondary namenode has these services:
The all the datanodes have the following services:
The manager has the following services: