Support Questions

Find answers, ask questions, and share your expertise
Announcements
Now Live: Explore expert insights and technical deep dives on the new Cloudera Community BlogsRead the Announcement

Who agreed with this solution

avatar
Rising Star

I found the solution for the above issue 

1) for protocolError we need to use kill -9 to kill the superviser

2) the above mention steps are correct I was making some typo with the ip and hostnames in the config.ini in one of the hosts.

 

Hope that help....

 

Thanks,

Amit

 

 

View solution in original post

Who agreed with this solution