About nallagangus

nallagangus · ‎05-05-2016

I figured this out. MR2 is listed as a service because MR history server is associated under that. Ambari could have simply named MR2 as MR2 history server which would probably avoided confusion. I know it is a silly distraction..

nallagangus · ‎05-05-2016

nallagangus · ‎01-05-2016

1) what is the recommendation to resolve scm-server issue? cloudera-scm-agent (pid 2250) is running... cloudera-scm-server dead but pid file exists.. A peek into /var/log/cloudera-scm-server refers to failed connectivity toDB server. Last acquisition attempt exception:com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure 2) What is the recommended approach for a multi-node cluster. I want to able to deploy datanodes on 2 containers and namenode on a 3'rd container. Do you have a tried solution? Sudhir

nallagangus · ‎12-16-2015

Do you have suggestions on next steps for posted error message for "scm-coudera-server" Also what is cloudera position on a multi-node cluster setup using docker containers ? I was recommended "cloudera director" - Is there a docker container available in that context?

nallagangus · ‎12-14-2015

My intent to start only desired services on "CDH" manually from CM. service cloudera-scm-server status ias follows: cloudera-scm-agent (pid 2250) is running... cloudera-scm-server dead but pid file exists.. A peek into /var/log/cloudera-scm-server refers to failed connectivity toDB server. Last acquisition attempt exception:com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure service mysqld status --> indicates it is running w/o issues. What config CM uses to connect to DB server? Sudhir

nallagangus · ‎12-14-2015

Thanks for prompt reply. I am more interested in finding out post "cloudera-manager" script all services are running. How do I validate if services required for CM are running ? Since I am on the container itself I can calidate locally w/o worry about port mappings on 7180. I am trying curl localhost:7180 and it says it is not responding Sudhir

nallagangus · ‎12-14-2015

Thanks Sean.. So technically I could run (I have enough memory) and I did run cloudera-manager directly once I logged onto bash. I see that many of services are disabled post cloudera-manager.sh exucution which is expected as per explanation. How do I cross validate all cluster-wide context services are running? while I got a successful message "please logon to quickstart.cloudera:7180" after script , I could not ping "using curl localhost:7180" . Sudhir

nallagangus · ‎12-14-2015

Hi I installed docker container and followed above instrucitons on a Windows laptop. Ran the two steps as mentioned (1. /usr/bin/docker-quickstart which lets me connect to Bash shell and 2. Clouder manager. ). When I do a service --status-all I see following message at end of 2 steps. cloudera-scm-agent (pid 2250) is running... cloudera-scm-server dead but pid file exists.. Many other Hadoop services are not running . Has any one tried this setup on a windows laptop? I do not understand why it has to be done in 2 steps when you could run everything in background with -d option. Especially step 2 of cloudera-manaher shutting down CDH services followed by CM_services start. I did notice difference in CM_services list between docker-quickstart.sh and cloudera-manager.sh scirpt Thanks Sudhir

Online	Offline
Last Visited	‎09-08-2016 09:55 AM

Member Since	‎12-14-2015 09:00 AM
Last Visited	‎09-08-2016 09:55 AM
Posts	14

Cloudera Community

Re: Why does Ambari treat YARN and MR2 as separate...

Why does Ambari treat YARN and MR2 as separate ser...

Re: Docker quickstart images issues on windows

Re: Docker quickstart images issues on windows

Re: Docker quickstart images issues on windows

Re: Docker quickstart images issues on windows

Re: Docker quickstart images issues on windows

Docker quickstart images issues on windows