Protocol message end-group tag did not match expected tag.

Showing 1-9 of 9 messages
Protocol message end-group tag did not match expected tag. Subroto 8/2/12 8:34 AM

I keep getting error:
==============================================================================================================
java.lang.reflect.UndeclaredThrowableException
at org.apache.hadoop.yarn.exceptions.impl.pb.YarnRemoteExceptionPBImpl.unwrapAndThrowException(YarnRemoteExceptionPBImpl.java:135)
at org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getClusterMetrics(ClientRMProtocolPBClientImpl.java:123)
at org.apache.hadoop.mapred.ResourceMgrDelegate.getClusterMetrics(ResourceMgrDelegate.java:151)
at org.apache.hadoop.mapred.YARNRunner.getClusterMetrics(YARNRunner.java:184)
at org.apache.hadoop.mapreduce.Cluster.getClusterStatus(Cluster.java:236)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:765)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:763)
at java.security.AccessController.doPrivileged(Native Method)
at javax.security.auth.Subject.doAs(Subject.java:396)
at org.apache.hadoop.security.UserGroupInformation.doAs(UserGroupInformation.java:1232)
at org.apache.hadoop.mapred.JobClient.getClusterStatus(JobClient.java:763)
******************************************************************************************
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:45)
at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:15)
at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:42)
at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:20)
at org.junit.internal.runners.statements.RunBefores.evaluate(RunBefores.java:28)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.rules.ExternalResource$1.evaluate(ExternalResource.java:46)
at org.junit.internal.runners.statements.FailOnTimeout$StatementThread.run(FailOnTimeout.java:62)
Caused by: com.google.protobuf.ServiceException: java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: Protocol message end-group tag did not match expected tag.; Host Details : local host is: "ssanyal.datameer.lan/192.168.178.58"; destination host is: "ec2-23-22-116-34.compute-1.amazonaws.com":8088; 
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:187)
at $Proxy39.getClusterMetrics(Unknown Source)
at org.apache.hadoop.yarn.api.impl.pb.client.ClientRMProtocolPBClientImpl.getClusterMetrics(ClientRMProtocolPBClientImpl.java:121)
... 27 more
Caused by: java.io.IOException: Failed on local exception: com.google.protobuf.InvalidProtocolBufferException: Protocol message end-group tag did not match expected tag.; Host Details : local host is: "ssanyal.xxxxx.lan/192.168.178.58"; destination host is: "ec2-23-22-116-34.compute-1.amazonaws.com":8088; 
at org.apache.hadoop.net.NetUtils.wrapException(NetUtils.java:765)
at org.apache.hadoop.ipc.Client.call(Client.java:1165)
at org.apache.hadoop.ipc.ProtobufRpcEngine$Invoker.invoke(ProtobufRpcEngine.java:184)
... 29 more
Caused by: com.google.protobuf.InvalidProtocolBufferException: Protocol message end-group tag did not match expected tag.
at com.google.protobuf.InvalidProtocolBufferException.invalidEndTag(InvalidProtocolBufferException.java:73)
at com.google.protobuf.CodedInputStream.checkLastTagWas(CodedInputStream.java:124)
at com.google.protobuf.AbstractMessageLite$Builder.mergeFrom(AbstractMessageLite.java:213)
at com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:746)
at com.google.protobuf.AbstractMessage$Builder.mergeFrom(AbstractMessage.java:238)
at com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:282)
at com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:760)
at com.google.protobuf.AbstractMessageLite$Builder.mergeDelimitedFrom(AbstractMessageLite.java:288)
at com.google.protobuf.AbstractMessage$Builder.mergeDelimitedFrom(AbstractMessage.java:752)
at org.apache.hadoop.ipc.protobuf.RpcPayloadHeaderProtos$RpcResponseHeaderProto.parseDelimitedFrom(RpcPayloadHeaderProtos.java:985)
at org.apache.hadoop.ipc.Client$Connection.receiveResponse(Client.java:850)
at org.apache.hadoop.ipc.Client$Connection.run(Client.java:781)
==============================================================================================================

Following is the stack where it breaks:
==============================================================================================================
Client.call(RPC$RpcKind, Writable, Client$ConnectionId) line: 1165
ProtobufRpcEngine$Invoker.invoke(Object, Method, Object[]) line: 184
$Proxy39.getClusterMetrics(RpcController, YarnServiceProtos$GetClusterMetricsRequestProto) line: not available
ClientRMProtocolPBClientImpl.getClusterMetrics(GetClusterMetricsRequest) line: 121
ResourceMgrDelegate.getClusterMetrics() line: 151
YARNRunner.getClusterMetrics() line: 184
Cluster.getClusterStatus() line: 236
JobClient$3.run() line: 765
JobClient$3.run() line: 763
AccessController.doPrivileged(PrivilegedExceptionAction<T>, AccessControlContext) line: not available [native method]
Subject.doAs(Subject, PrivilegedExceptionAction<T>) line: 396
UserGroupInformation.doAs(PrivilegedExceptionAction<T>) line: 1232
JobClient.getClusterStatus() line: 763
==============================================================================================================

I am using CDH4u0 release.

Cheers,
Subroto Sanyal
Re: Protocol message end-group tag did not match expected tag. Aaron T. Myers 8/2/12 9:25 AM
Hi Subroto,

What action are you performing when you see this error?

--
Aaron T. Myers
Software Engineer, Cloudera



--
 
 
 

Re: Protocol message end-group tag did not match expected tag. Subroto 8/2/12 9:31 AM
Hi Aaron,
I am trying to run a MR job when it breaks:

at org.apache.hadoop.mapred.YARNRunner.getClusterMetrics(YARNRunner.java:184)
at org.apache.hadoop.mapreduce.Cluster.getClusterStatus(Cluster.java:236)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:765)
at org.apache.hadoop.mapred.JobClient$3.run(JobClient.java:763)

Cheers,
Subroto Sanyal

--
 
 
 

Re: Protocol message end-group tag did not match expected tag. Subroto 8/3/12 2:53 AM
Hi Aaron,

The message being sent over RPC is:

=========================================

methodName: "getClusterMetrics"

request: ""

declaringClassProtocolName: "org.apache.hadoop.yarn.api.ClientRMProtocolPB"

clientProtocolVersion: 1

=========================================

Cheers,
Subroto Sanyal
Re: Protocol message end-group tag did not match expected tag. Todd Lipcon 8/3/12 12:13 PM
Hi Subroto,

Are you sure you're sending it to the right host/port? Perhaps you're
sending it to an HTTP port, or to a machine running the MR1 JobTracker
rather than the RM?

-Todd
> --
>
>
>



--
Todd Lipcon
Software Engineer, Cloudera
Re: Protocol message end-group tag did not match expected tag. Subroto 8/6/12 1:47 AM
Hi Todd,

It was my mistake in configuring the ports in the code.
Instead of passing the correct "yarn.resourcemanager.address", I was passing "yarn.resourcemanager.webapp.address".

Thanks Todd and Aaron.....

Cheers,
Subroto Sanyal

--




Re: Protocol message end-group tag did not match expected tag. ashok kumar 5/3/13 7:24 AM
I'm also getting the same error but i can't find the solution. Here my yarn-site.xml pls help me...
<?xml version="1.0"?>
<configuration>
 
  <property>
    <name>yarn.resourcemanager.address</name>
    <value>localhost:10040</value>
    <description>In Server specified the port that Resource Manager will runn on. In client is used for connecting to Resource Manager</description>
  </property>
  <property>
    <name>yarn.resourcemanager.resource-tracker.address</name>
    <value>localhost:8025</value>
    <description>Utilized by Node Manager for communication with Resource Manager</description>
  </property>
  <property>
    <name>yarn.resourcemanager.scheduler.address</name>
    <value>localhost:8030</value>
     <description>Utilized by Application Masters to communicate with Resource Manager; in our case for MRAppMaster (MapReduce Application Master) to communicate with Resource Manager</description>
  </property>
  <property>
    <name>yarn.resourcemanager.admin.address</name>
    <value>localhost:8141</value>
     <description>Utilized by administrative clients ($yarn rmadmin) to communicate with Resource Manager</description>
  </property>

  <property>
     <name>yarn.nodemanager.local-dirs</name>
     <value>/app/hadoop</value>
     <final>true</final>
     <description>Comma separated list of directories, where local data is persisted by Node Manager</description>
  </property>

  <property>
     <name>yarn.nodemanager.aux-services</name>
     <value>mapreduce.shuffle</value>
     <description>Long running service which executes on Node Manager(s) and provides MapReduce Sort and Shuffle functionality.</description>
  </property>

  <property>
     <name>yarn.log-aggregation-enable</name>
     <value>true</value>
    <description>Enable log aggregation so application logs are moved onto hdfs and are viewable via web ui after the application completed. The default location on hdfs is '/log' and can be changed via yarn.nodemanager.remote-app-log-dir property</description>
  </property>

 <property>
     <name>hadoop.security.authorization</name>
     <value>false</value>
     <description>Disable authorization fo development and clusters that do not require security</description>
   </property>

</configuration>
Re: Protocol message end-group tag did not match expected tag. Tony Tony 5/11/15 10:53 AM
Did you ever resolve this?
Re: Protocol message end-group tag did not match expected tag. Harsh J 5/11/15 12:49 PM
Tony,

You will get this form of an error if you are trying to connect to an HTTP port instead of the RPC one. You need to review the connection URL shown in the output and determine if its the right port your program is connecting to for the function attempted.

In the original issue, the RPC port being used per the error was 8088, which is actually a HTTP port instead.

--

---
You received this message because you are subscribed to the Google Groups "CDH Users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to cdh-user+u...@cloudera.org.
For more options, visit https://groups.google.com/a/cloudera.org/d/optout.



--
Harsh J