Grokbase › Groups › Hadoop › scm-users › December 2012
FAQ
Hello guys,

my situation is as such: I set up a 1 node cluster of hadoop/hbase, but had
to stop the EC2 instance.
After I've started the server again, its IP has changed therefore none of
the services may be monitored or started.

Cloudera manager sees the same old IP address and i can not find a way to
change it. Any clue?
So far I imagine I would have to go to cloudera's and every service config
file and edit the address manually. Is this the way?

Thanks!
Gintas

Search Discussions

  • Philip Zeyliger at Dec 13, 2012 at 5:08 am ⇧
    Hi Gintas,

    This is one of the more, um, irritating bits about EC2. You should edit
    /etc/cloudera-scm-agent/config.ini to point to the server's new IP. You
    should also edit /etc/default/cloudera-scm-agent to have
    CMF_AGENT_ARGS="--host_id xxx" where xxx is any unique identifier you want
    to use. Currently the system thinks it's the hostname of your original EC2
    box, but that might end up being confusing. You might need to edit the
    HOSTS table in the CM database (as configured in
    /etc/cloudera-scm-server/db.properties) to remap the identifier; there's no
    easy way to move hosts otherwise.

    Hope this helps,

    -- Philip
    On Wed, Dec 12, 2012 at 6:03 PM, Gintautas Sulskus wrote:

    Hello guys,

    my situation is as such: I set up a 1 node cluster of hadoop/hbase, but
    had to stop the EC2 instance.
    After I've started the server again, its IP has changed therefore none of
    the services may be monitored or started.

    Cloudera manager sees the same old IP address and i can not find a way to
    change it. Any clue?
    So far I imagine I would have to go to cloudera's and every service config
    file and edit the address manually. Is this the way?

    Thanks!
    Gintas
  • Mark Grover at Dec 14, 2012 at 12:58 am ⇧
    Gintas,
    To add to Philip's comment, if you'd like to restart your nodes frequently,
    consider associating an Elastic IP with them and use that IP in your
    Cloudera Manager configuration(s).

    Mark
    On Wed, Dec 12, 2012 at 9:07 PM, Philip Zeyliger wrote:

    Hi Gintas,

    This is one of the more, um, irritating bits about EC2. You should edit
    /etc/cloudera-scm-agent/config.ini to point to the server's new IP. You
    should also edit /etc/default/cloudera-scm-agent to have
    CMF_AGENT_ARGS="--host_id xxx" where xxx is any unique identifier you want
    to use. Currently the system thinks it's the hostname of your original EC2
    box, but that might end up being confusing. You might need to edit the
    HOSTS table in the CM database (as configured in
    /etc/cloudera-scm-server/db.properties) to remap the identifier; there's no
    easy way to move hosts otherwise.

    Hope this helps,

    -- Philip

    On Wed, Dec 12, 2012 at 6:03 PM, Gintautas Sulskus wrote:

    Hello guys,

    my situation is as such: I set up a 1 node cluster of hadoop/hbase, but
    had to stop the EC2 instance.
    After I've started the server again, its IP has changed therefore none of
    the services may be monitored or started.

    Cloudera manager sees the same old IP address and i can not find a way to
    change it. Any clue?
    So far I imagine I would have to go to cloudera's and every service
    config file and edit the address manually. Is this the way?

    Thanks!
    Gintas
  • Gintautas Sulskus at Dec 14, 2012 at 1:52 am ⇧
    Thank you very much, guys!

    I will try these solutions as soon as possible and give my feedback!

    Cheers,
    Gintautas
    On Fri, Dec 14, 2012 at 12:51 AM, Mark Grover wrote:

    Gintas,
    To add to Philip's comment, if you'd like to restart your nodes
    frequently, consider associating an Elastic IP with them and use that IP in
    your Cloudera Manager configuration(s).

    Mark

    On Wed, Dec 12, 2012 at 9:07 PM, Philip Zeyliger wrote:

    Hi Gintas,

    This is one of the more, um, irritating bits about EC2. You should edit
    /etc/cloudera-scm-agent/config.ini to point to the server's new IP. You
    should also edit /etc/default/cloudera-scm-agent to have
    CMF_AGENT_ARGS="--host_id xxx" where xxx is any unique identifier you want
    to use. Currently the system thinks it's the hostname of your original EC2
    box, but that might end up being confusing. You might need to edit the
    HOSTS table in the CM database (as configured in
    /etc/cloudera-scm-server/db.properties) to remap the identifier; there's no
    easy way to move hosts otherwise.

    Hope this helps,

    -- Philip

    On Wed, Dec 12, 2012 at 6:03 PM, Gintautas Sulskus wrote:

    Hello guys,

    my situation is as such: I set up a 1 node cluster of hadoop/hbase, but
    had to stop the EC2 instance.
    After I've started the server again, its IP has changed therefore none
    of the services may be monitored or started.

    Cloudera manager sees the same old IP address and i can not find a way
    to change it. Any clue?
    So far I imagine I would have to go to cloudera's and every service
    config file and edit the address manually. Is this the way?

    Thanks!
    Gintas

    --
    Best Regards,
    Gintautas Sulskus

Related Discussions

Discussion Navigation
viewthread | post
Discussion Overview
groupscm-users @
categorieshadoop
postedDec 13, '12 at 2:03a
activeDec 14, '12 at 1:52a
posts4
users3
websitecloudera.com
irc#hadoop

3 users in discussion

Gintautas Sulskus: 2 posts Philip Zeyliger: 1 post Mark Grover: 1 post

Content

People

Support

Translate

site design / logo © 2023 Grokbase