Reply
Explorer
Posts: 12
Registered: ‎02-15-2016

Unable to add Kudu service to the cluster - CDH v5.7.1

[ Edited ]

I want to deploy Kudu and test with it. However, I am unable to add the service via Cloudera Manager even though I am using Cloudera's Parcel installation method given at the following URL:

http://www.cloudera.com/downloads/beta/kudu/1-0-1.html

 

I am able to distribute and activate the parcel, but when I try to add the Kudu service it fails while starting the service. I get the following errors:

 

Kudu Master - 

Command aborted because of exception: Command timed-out after 150 seconds

Tablet Server - 

Supervisor returned FATAL. Please check the role log file, stderr, or stdout.

Error found before invoking supervisord: No parcel provided required tags: set([u'kudu'])

 

Upon looking in the cloudera-scm-server logs, I see the following:

 

2016-11-12 08:58:47,623 INFO 746446932@scm-web-12:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing service command Restart SvcCmdArgs{targetRoles=[DbRole{id=170, name=kudu-KUDU_TSERVER-1183ed869254bc13f619cfaad2e39403, hostName=usmtnz-dinfap69.emrsn.org}, DbRole{id=169, name=kudu-KUDU_MASTER-c48d865faa50d30f512a1c2d917045e2, hostName=usmtnz-dinfap67.emrsn.org}], args=[]}. Service: DbService{id=36, name=kudu}
2016-11-12 08:58:47,638 INFO 746446932@scm-web-12:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing service command Start SvcCmdArgs{targetRoles=[DbRole{id=170, name=kudu-KUDU_TSERVER-1183ed869254bc13f619cfaad2e39403, hostName=usmtnz-dinfap69.emrsn.org}, DbRole{id=169, name=kudu-KUDU_MASTER-c48d865faa50d30f512a1c2d917045e2, hostName=usmtnz-dinfap67.emrsn.org}], args=[]}. Service: DbService{id=36, name=kudu}
2016-11-12 08:58:47,642 INFO 746446932@scm-web-12:com.cloudera.cmf.service.AbstractBringUpBringDownCommands: Added BringUp command to service DbService{id=36, name=kudu}.
2016-11-12 08:58:47,652 INFO 746446932@scm-web-12:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing role command Start BasicCmdArgs{args=[]}. Service: DbService{id=36, name=kudu} Role: DbRole{id=170, name=kudu-KUDU_TSERVER-1183ed869254bc13f619cfaad2e39403, hostName=usmtnz-dinfap69.emrsn.org}
2016-11-12 08:58:47,714 INFO 746446932@scm-web-12:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing role command Start BasicCmdArgs{args=[]}. Service: DbService{id=36, name=kudu} Role: DbRole{id=169, name=kudu-KUDU_MASTER-c48d865faa50d30f512a1c2d917045e2, hostName=usmtnz-dinfap67.emrsn.org}
2016-11-12 08:58:47,979 INFO 746446932@scm-web-12:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing command ProcessStalenessCheckCommand BasicCmdArgs{args=[First reason why: com.cloudera.cmf.model.DbConfig.valueForDb (#575) has changed]}.
2016-11-12 08:58:48,164 WARN 1582365219@agentServer-0:com.cloudera.server.cmf.AgentProtocolImpl: Received Process Heartbeat for unknown (or duplicate) process. Ignoring. This is expected to happen once after old process eviction or process deletion (as happens in restarts). id=21220 name=null host=d85ff2c1-280e-413f-96d1-66aee00e292c/usmtnz-dinfap67.emrsn.org
2016-11-12 08:58:50,628 INFO ProcessStalenessDetector-0:com.cloudera.cmf.service.config.components.ProcessStalenessDetector: Staleness check done. Duration: PT2.548S
2016-11-12 08:59:03,429 INFO 1582365219@agentServer-0:com.cloudera.cmf.command.components.StalenessChecker: No staleness check scheduled, scheduling one in 30 seconds
2016-11-12 08:59:03,510 INFO CommandPusher:com.cloudera.cmf.service.GenericBringUpRoleCommand: BringUp command (53399) has finished on service kudu for role 170/kudu-KUDU_TSERVER-1183ed869254bc13f619cfaad2e39403, with status FAILURE and message MessageWithArgs{messageId=message.command.role.bringUp.supervisor.fatal, args=[]}
2016-11-12 08:59:03,510 INFO CommandPusher:com.cloudera.cmf.model.DbCommand: Command 53399(Start) has completed. finalstate:FINISHED, success:false, msg:Failed to start role.
2016-11-12 08:59:33,430 INFO ScheduledStalenessChecker:com.cloudera.cmf.service.ServiceHandlerRegistry: Executing command ProcessStalenessCheckCommand BasicCmdArgs{args=[First reason why: Process (id=21221) has a brand new heartbeat]}.
2016-11-12 08:59:35,980 INFO ProcessStalenessDetector-0:com.cloudera.cmf.service.config.components.ProcessStalenessDetector: Staleness check done. Duration: PT2.521S

2016-11-12 09:01:21,486 INFO CommandPusher:com.cloudera.cmf.service.GenericBringUpRoleCommand: BringUp command (53400) has finished on service kudu for role 169/kudu-KUDU_MASTER-c48d865faa50d30f512a1c2d917045e2, with status ABORTED and message MessageWithArgs{messageId=message.command.role.bringUp.starting, args=[]}
2016-11-12 09:01:21,487 INFO CommandPusher:com.cloudera.cmf.model.DbCommand: Command 53400(Start) has completed. finalstate:CANCELLED, success:false, msg:Aborted command
2016-11-12 09:01:21,521 INFO CommandPusher:com.cloudera.cmf.model.DbCommand: Command 53398(Start) has completed. finalstate:FINISHED, success:false, msg:Failed to start service.
2016-11-12 09:01:21,522 INFO CommandPusher:com.cloudera.cmf.model.DbCommand: Command 53397(Restart) has completed. finalstate:FINISHED, success:false, msg:Failed to restart service.
2016-11-12 09:01:33,313 WARN 1582365219@agentServer-0:com.cloudera.server.cmf.AgentProtocolImpl: Received Process Heartbeat for unknown (or duplicate) process. Ignoring. This is expected to happen once after old process eviction or process deletion (as happens in restarts). id=21222 name=null host=d85ff2c1-280e-413f-96d1-66aee00e292c/usmtnz-dinfap67.emrsn.org
2016-11-12 09:02:42,180 INFO StaleEntityEviction:com.cloudera.server.cmf.StaleEntityEvictionThread: Reaped total of 0 deleted commands
2016-11-12 09:02:42,201 INFO StaleEntityEviction:com.cloudera.server.cmf.StaleEntityEvictionThread: Found no commands older than 2014-11-13T09:02:42.181Z to reap.
2016-11-12 09:02:42,204 INFO StaleEntityEviction:com.cloudera.server.cmf.node.NodeScannerService: Reaped 0 requests.
2016-11-12 09:02:42,204 INFO StaleEntityEviction:com.cloudera.server.cmf.node.NodeConfiguratorService: Reaped 0 requests.

 

 

Please help me in fixing this issue.

 

Regards,

Mohit

 

Highlighted
Explorer
Posts: 12
Registered: ‎02-15-2016

Re: Unable to add Kudu service to the cluster - CDH v5.7.1

Nevermind! I was able to find the cause of this. Somehow, I had missed activating the parcel in CM which is why it was throwing this error(s).
Announcements