FAQ

On Friday, 1 February 2013 06:32:39 UTC, Philip Zeyliger wrote:
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.

If you use an external rather than embedded database it's feasible to
provide for a more highly available solution via postgres replication and
pooling via a tool like pgpool-II

You could, in theory, have a standby cloudera manager server pointed to
that and ready to start the services on and change DNS/IPs etc to point to
that...

It would of course be important to have suitable fencing or other methods
(use stuff like pacemaker etc) to ensure services did not run on both nodes
at the same time and avoid split-brain situations and so on ...

You're talking about the cloudera manager 'machine' being completely
lost... if you virtualize SCM that of course can provide additional
resilience and flexibility too...

James

Search Discussions

Discussion Posts

Previous

Related Discussions

Discussion Navigation
viewthread | post
posts ‹ prev | 4 of 4 | next ›
Discussion Overview
groupscm-users @
categorieshadoop
postedFeb 1, '13 at 6:23a
activeFeb 1, '13 at 11:13a
posts4
users3
websitecloudera.com
irc#hadoop

People

Translate

site design / logo © 2022 Grokbase