On Wed, Jun 19, 2013 at 1:00 PM, Aaron T. Myers wrote:
Hi Mukhtaj,
Moving this over to [email protected], which should be able to help
you with this issue.
--
Aaron T. Myers
Software Engineer, Cloudera
Hi Mukhtaj,
Moving this over to [email protected], which should be able to help
you with this issue.
--
Aaron T. Myers
Software Engineer, Cloudera
On Tue, Jun 18, 2013 at 4:11 AM, Mukhtaj Khan wrote:
I had move the cluster to new location. I have updated /etc/hosts file
with new IP address. Now I have checked the CM WebAPI, It show that all
hosts have bad health. It also shows the old IP address. I have run the
Host inspector but does not working. What I should do? How I can restart
the cluster so it pick the new IP address.
Many thanks
Bets regards,
---
You received this message because you are subscribed to the Google Groups
"CDH Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit
https://groups.google.com/a/cloudera.org/groups/opt_out.
I had move the cluster to new location. I have updated /etc/hosts file
with new IP address. Now I have checked the CM WebAPI, It show that all
hosts have bad health. It also shows the old IP address. I have run the
Host inspector but does not working. What I should do? How I can restart
the cluster so it pick the new IP address.
Many thanks
Bets regards,
On Thu, Mar 21, 2013 at 5:40 PM, Mukhtaj Khan wrote:
Dear Subbu
Many thanks for suggestion.
Best regards,
M Khan
On Sun, Mar 17, 2013 at 4:05 PM, Subramanyam Malepati <
[email protected]> wrote:
--Dear Subbu
Many thanks for suggestion.
Best regards,
M Khan
On Sun, Mar 17, 2013 at 4:05 PM, Subramanyam Malepati <
[email protected]> wrote:
If you are using FQDN hostnames in config files, it should not matter.
If you have used IP addresses in the config files, then you have to
modify all the config files to make it work.
I suggest use FQDN names if not exists.
Also try to use private IP on eth1 wherever possible and make use of
/etc/hosts file to update new ip addresses and mapping.
regards
Subbu
If you have used IP addresses in the config files, then you have to
modify all the config files to make it work.
I suggest use FQDN names if not exists.
Also try to use private IP on eth1 wherever possible and make use of
/etc/hosts file to update new ip addresses and mapping.
regards
Subbu
On Sun, Mar 17, 2013 at 6:55 AM, Mukhtaj Khan wrote:
Dear all,
I want to move my virtual cluster to another building where the IP
address of network is different. I would be install and configure again the
CDH or there is any other easy way.
Thanks
Best regards,
--
--Dear all,
I want to move my virtual cluster to another building where the IP
address of network is different. I would be install and configure again the
CDH or there is any other easy way.
Thanks
Best regards,
--
---
You received this message because you are subscribed to the Google Groups
"CDH Users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to [email protected].
For more options, visit
https://groups.google.com/a/cloudera.org/groups/opt_out.