Archives of Support Questions (Read Only)

This is an archived board for historical reference. Information and links may no longer be available or relevant
Announcements
This board is archived and read-only for historical reference. To ask a new question, please post a new topic on the appropriate active board.

Accumulo parcel distributing error

avatar
Explorer

Hello,

 

I am getting following errors while try to distribute accumulo parcel in 2 node cluster.

 

  • Error when distributing to telecom : Ignoring non-compliant parcel manifest: ACCUMULO-1.4.4-1.cdh4.5.0.p0.65.

I have installed the proper CDH version required for accumulo installation but it is still giving this error. If some can point me in the right direction to solve this issue, I will be grateful.

 

Error screenshot:

 

Screenshot from 2014-03-19 18:32:26.png

 

Server log:

 

2014-03-19 18:16:22,969  INFO [CommandPusher:service.FirstRunCommand@331] Internal State: [State: cmdName='ServiceWaitCommand', entityName='zookeeper1', processName='null', State: cmdName='Start', entityName='zookeeper1', processName='null', State: cmdName='Format', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-format', State: cmdName='Start', entityName='hdfs1', processName='null', State: cmdName='CreateTmp', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-createtmp', State: cmdName='Start', entityName='mapreduce1', processName='null', State: cmdName='Start', entityName='mgmt1', processName='null', State: cmdName='DeployClusterClientConfig', entityName='Cluster 1 - CDH4', processName='null']
2014-03-19 18:16:25,982  WARN [785426145@agentServer-12:cmf.AgentProtocolImpl@493] 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=26 name=null host=telecom/telecom
2014-03-19 18:16:26,418  INFO [CommandPusher:command.CommandHelpers@199] Command (deployClientConfig, 271) is still active on service DbService{id=9, name=mapreduce1, serviceType=MAPREDUCE, optimisticLockVersion=2, cluster=DbCluster{id=5, name=Cluster 1 - CDH4, version=4, maintenanceCount=0}, maintenanceCount=0}.
2014-03-19 18:16:26,419  INFO [CommandPusher:service.FirstRunCommand@331] Internal State: [State: cmdName='ServiceWaitCommand', entityName='zookeeper1', processName='null', State: cmdName='Start', entityName='zookeeper1', processName='null', State: cmdName='Format', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-format', State: cmdName='Start', entityName='hdfs1', processName='null', State: cmdName='CreateTmp', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-createtmp', State: cmdName='Start', entityName='mapreduce1', processName='null', State: cmdName='Start', entityName='mgmt1', processName='null', State: cmdName='DeployClusterClientConfig', entityName='Cluster 1 - CDH4', processName='null']
2014-03-19 18:16:27,462  INFO [CommandPusher:service.AbstractOneOffHostCommand@124] Successful 'deployClientConfig'
2014-03-19 18:16:27,487  INFO [CommandPusher:command.CommandHelpers@206] Command (deployClientConfig, 271) has finished on service DbService{id=9, name=mapreduce1, serviceType=MAPREDUCE, optimisticLockVersion=2, cluster=DbCluster{id=5, name=Cluster 1 - CDH4, version=4, maintenanceCount=0}, maintenanceCount=0}.
2014-03-19 18:16:27,489  INFO [CommandPusher:service.FirstRunCommand@331] Internal State: [State: cmdName='ServiceWaitCommand', entityName='zookeeper1', processName='null', State: cmdName='Start', entityName='zookeeper1', processName='null', State: cmdName='Format', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-format', State: cmdName='Start', entityName='hdfs1', processName='null', State: cmdName='CreateTmp', entityName='hdfs1-NAMENODE-29e7396b6b7e8b8ab20daabcde1c7732', processName='hdfs-NAMENODE-createtmp', State: cmdName='Start', entityName='mapreduce1', processName='null', State: cmdName='Start', entityName='mgmt1', processName='null', State: cmdName='DeployClusterClientConfig', entityName='Cluster 1 - CDH4', processName='null']
2014-03-19 18:16:27,490  INFO [CommandPusher:service.FirstRunCommand@363] First Run Complete.
2014-03-19 18:17:14,704  INFO [360322406@scm-web-36:components.ParcelManagerImpl@313] Distributing parcel ACCUMULO:1.4.4-1.cdh4.5.0.p0.65 on cluster Cluster 1 - CDH4
2014-03-19 18:17:15,751  INFO [1071845863@scm-web-34:cmf.ParcelController@241] Served parcel ACCUMULO-1.4.4-1.cdh4.5.0.p0.65-precise.parcel (11305840 bytes) to 192.168.2.109 over PT0.833S.  Rate: 12.944 MB/s
2014-03-19 18:17:28,363  INFO [360322406@scm-web-36:cmf.ParcelController@241] Served parcel ACCUMULO-1.4.4-1.cdh4.5.0.p0.65-precise.parcel (11305840 bytes) to 192.168.2.124 over PT0.830S.  Rate: 12.990 MB/s
2014-03-19 18:22:03,388  INFO [StaleEntityEviction:model.HeartbeatStore@107] Reaped 0 process heartbeats and 0 host heartbeats.
2014-03-19 18:22:03,421  INFO [StaleEntityEviction:cmf.StaleEntityEvictionThread@233] Found no commands older than 2012-03-19T13:22:03.396Z to reap.
2014-03-19 18:22:03,424  INFO [StaleEntityEviction:node.NodeScannerService@335] Reaped 0 requests.
2014-03-19 18:22:03,432  INFO [StaleEntityEviction:node.NodeConfiguratorService@327] Reaped 0 requests.
2014-03-19 18:32:03,435  INFO [StaleEntityEviction:model.HeartbeatStore@107] Reaped 4 process heartbeats and 0 host heartbeats.
2014-03-19 18:32:03,445  INFO [StaleEntityEviction:cmf.StaleEntityEvictionThread@233] Found no commands older than 2012-03-19T13:32:03.443Z to reap.
2014-03-19 18:32:03,448  INFO [StaleEntityEviction:node.NodeScannerService@335] Reaped 0 requests.
2014-03-19 18:32:03,448  INFO [StaleEntityEviction:node.NodeConfiguratorService@327] Reaped 0 requests.
1 ACCEPTED SOLUTION

avatar
Expert Contributor

That's the problem then. The parcel for Accumulo 1.4.4-cdh4.5.0 relies on the extensibility additions in Cloudera Manager 5 beta 2.

 

Can you update your Cloudera Manager version and try again?

 

While Cloudera Manager 5 is in beta, it can happily install and manage any of our stable CDH releases, including the recommended version for running our latest Accumulo release: CDH 4.5.0.

View solution in original post

4 REPLIES 4

avatar
Expert Contributor

Hi Adnan!

 

What version of Cloudera Manager are you using?

avatar
Explorer
I am using Cloudera Manager 4.8.2.

avatar
Expert Contributor

That's the problem then. The parcel for Accumulo 1.4.4-cdh4.5.0 relies on the extensibility additions in Cloudera Manager 5 beta 2.

 

Can you update your Cloudera Manager version and try again?

 

While Cloudera Manager 5 is in beta, it can happily install and manage any of our stable CDH releases, including the recommended version for running our latest Accumulo release: CDH 4.5.0.

avatar
Explorer
It worked. Thanks for your help.