Member since
10-21-2017
2
Posts
0
Kudos Received
0
Solutions
10-21-2017
07:40 PM
Thank you for this excellent solution. In my situation, I created 1 master and 4 slaves cloudera cluster using private IP with EC2 and then store then as AMI (images). I then created newinstances from these 5 AMI images, with all installations of cloudera on them. Then I folllowed all your steps to change the IP to current private IPs. However, when I finally check the state of the cloudera: sudo service cloudera-scm-agent status sudo service cloudera-scm-master status both return active (exited) Then I checked the /var/log/cloudera-scm-agent/cloudera-scm-agent.log And there are errors like this ERROR Failed to connect to previous supervisor. ERROR Failed rack peer update: [Errno 111] Connection refused ERROR 14794 Monitor-HostMonitor throttling_logger ERROR Failed to collect NTP metrics ERROR Unexpected exception during download Do you know why this happens? ( I followed all yoursteps)
... View more