Yes. If the hostname of the CM server changes, edit
/etc/cloudera-scm-agent/config.ini, and do a "service cloudera-scm-agent
restart" to have the agents pick up the new hostname. All of the
non-transient CM state is in that database.

-- Philip

On Thu, Jan 31, 2013 at 10:27 PM, David Montgomery wrote:


So e.g. you back up the database once an hour and place e.g. on s3. If
you boot a new manager node then restore the backup?

then back to normal?


On Fri, Feb 1, 2013 at 2:22 PM, Philip Zeyliger wrote:

Hi Pankaj,

We recommend you make a backup of the CM embedded database (e.g., with
pg_dump). Doing so will let you rebuild the machine on another host.
While the CM server is unavailable, Hadoop will continue running as before.

-- Philip

On Thu, Jan 31, 2013 at 4:57 PM, Mark Grover wrote:

Moving to scm-users@cloudera.org
(bcc: cdh-user@cloudera.org)
On Thu, Jan 31, 2013 at 4:56 PM, Pankaj Gupta wrote:


I'm just setting up a cluster using Cloudera Manager using the embedded
database option. I'm wondering about how to handle failure of Cloudera
Manager machine. Supposing that Cloudera Manager machine is completely lost
and I set up a new one and point the agents to it, would the new manager be
able to get relevant information from agents? If not then which files from
the embedded database do I need to take snapshots of? Basically what's the
recommended way of recovering from Cloudera Manager failure.

Thanks in Advance,


Search Discussions

Discussion Posts


Follow ups

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 3 of 4 | next ›
Discussion Overview
groupscm-users @
postedFeb 1, '13 at 6:23a
activeFeb 1, '13 at 11:13a



site design / logo © 2022 Grokbase