Re: Error register getProtocolVersion

Brian Bockelman Wed, 14 Oct 2009 09:24:22 -0700

Hey Tim,

That was my best guess - looks like you've got the right metrics config.


Anyone else have an idea?

Brian

On Oct 14, 2009, at 9:37 AM, tim robertson wrote:

Hi Brian,

Thanks for replying.    I don't even know what the metrics really are
so have never knowingly touched them.  I have only done the basic core
and site configuration along with master / slaves list and then a
namenode format and started the cluster to get this error.  All based
on the current 0.20.1 download on apache.

I think I am using the NullContext looking at the properties file...
could you please verify this is correct?

Many thanks for your help!
Tim


# Configuration of the "dfs" context for null
dfs.class=org.apache.hadoop.metrics.spi.NullContext

# Configuration of the "dfs" context for file
#dfs.class=org.apache.hadoop.metrics.file.FileContext
#dfs.period=10
#dfs.fileName=/tmp/dfsmetrics.log

# Configuration of the "dfs" context for ganglia
# dfs.class=org.apache.hadoop.metrics.ganglia.GangliaContext
# dfs.period=10
# dfs.servers=localhost:8649


# Configuration of the "mapred" context for null
mapred.class=org.apache.hadoop.metrics.spi.NullContext

# Configuration of the "mapred" context for file
#mapred.class=org.apache.hadoop.metrics.file.FileContext
#mapred.period=10
#mapred.fileName=/tmp/mrmetrics.log

# Configuration of the "mapred" context for ganglia
# mapred.class=org.apache.hadoop.metrics.ganglia.GangliaContext
# mapred.period=10
# mapred.servers=localhost:8649


# Configuration of the "jvm" context for null
jvm.class=org.apache.hadoop.metrics.spi.NullContext

# Configuration of the "jvm" context for file
#jvm.class=org.apache.hadoop.metrics.file.FileContext
#jvm.period=10
#jvm.fileName=/tmp/jvmmetrics.log

# Configuration of the "jvm" context for ganglia
# jvm.class=org.apache.hadoop.metrics.ganglia.GangliaContext
# jvm.period=10
# jvm.servers=localhost:8649

On Wed, Oct 14, 2009 at 3:12 PM, Brian Bockelman <bbock...@cse.unl.edu> wrote:

Hey Tim,

Can you see if that goes away if you use the null metrics context (the error

appears to be coming from metrics - have you touched them?)?

Brian

On Oct 14, 2009, at 4:33 AM, tim robertson wrote:

Hi all,

Using hadoop 0.20.1 I am seeing the following on my namenode startup.


2009-10-14 11:09:54,232 INFO org.apache.hadoop.ipc.Server: Error
register getProtocolVersion
java.lang.IllegalArgumentException: Duplicate
metricsName:getProtocolVersion

Could someone please point me in the right direction for diagnosing
where I have gone wrong?

Thanks
Tim



/************************************************************
STARTUP_MSG: Starting NameNode
STARTUP_MSG:   host = cluma.gbif.org/192.38.28.77
STARTUP_MSG:   args = []
STARTUP_MSG:   version = 0.20.1
STARTUP_MSG:   build =

http://svn.apache.org/repos/asf/hadoop/common/tags/release-0.20.1- rc1

-r 810220; compiled by 'oom' on Tue Sep  1 20:55:56 UTC 2009
************************************************************/

2009-10-14 11:09:53,010 INFO org.apache.hadoop.ipc.metrics.RpcMetrics:

Initializing RPC Metrics with hostName=NameNode, port=8020
2009-10-14 11:09:53,013 INFO
org.apache.hadoop.hdfs.server.namenode.NameNode: Namenode up at:
cluma.gbif.clu/192.168.76.254:8020

2009-10-14 11:09:53,015 INFO org.apache.hadoop.metrics.jvm.JvmMetrics:

Initializing JVM Metrics with processName=NameNode, sessionId=null
2009-10-14 11:09:53,019 INFO
org.apache.hadoop.hdfs.server.namenode.metrics.NameNodeMetrics:
Initializing NameNodeMeterics using context
object:org.apache.hadoop.metrics.spi.NullContext
2009-10-14 11:09:53,056 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
fsOwner=root,root,bin,daemon,sys,adm,disk,wheel
2009-10-14 11:09:53,057 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
supergroup=supergroup
2009-10-14 11:09:53,057 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem:
isPermissionEnabled=true
2009-10-14 11:09:53,064 INFO
org.apache.hadoop.hdfs.server.namenode.metrics.FSNamesystemMetrics:
Initializing FSNamesystemMetrics using context
object:org.apache.hadoop.metrics.spi.NullContext
2009-10-14 11:09:53,065 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Registered
FSNamesystemStatusMBean
2009-10-14 11:09:53,090 INFO
org.apache.hadoop.hdfs.server.common.Storage: Number of files = 1
2009-10-14 11:09:53,094 INFO
org.apache.hadoop.hdfs.server.common.Storage: Number of files under
construction = 0
2009-10-14 11:09:53,094 INFO
org.apache.hadoop.hdfs.server.common.Storage: Image file of size 94
loaded in 0 seconds.
2009-10-14 11:09:53,094 INFO
org.apache.hadoop.hdfs.server.common.Storage: Edits file
/hadoop/name/current/edits of size 4 edits # 0 loaded in 0 seconds.
2009-10-14 11:09:53,098 INFO
org.apache.hadoop.hdfs.server.common.Storage: Image file of size 94
saved in 0 seconds.
2009-10-14 11:09:53,113 INFO

org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Finished loading

FSImage in 72 msecs
2009-10-14 11:09:53,114 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Total number of
blocks = 0
2009-10-14 11:09:53,114 INFO

org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Number of invalid

blocks = 0
2009-10-14 11:09:53,114 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Number of
under-replicated blocks = 0
2009-10-14 11:09:53,114 INFO
org.apache.hadoop.hdfs.server.namenode.FSNamesystem: Number of
over-replicated blocks = 0
2009-10-14 11:09:53,114 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Leaving safe mode after 0 secs.
2009-10-14 11:09:53,114 INFO org.apache.hadoop.hdfs.StateChange:
STATE* Network topology has 0 racks and 0 datanodes
2009-10-14 11:09:53,114 INFO org.apache.hadoop.hdfs.StateChange:
STATE* UnderReplicatedBlocks has 0 blocks
2009-10-14 11:09:53,198 INFO org.mortbay.log: Logging to
org.slf4j.impl.Log4jLoggerAdapter(org.mortbay.log) via
org.mortbay.log.Slf4jLog
2009-10-14 11:09:53,242 INFO org.apache.hadoop.http.HttpServer: Port

returned by webServer.getConnectors()[0].getLocalPort() before open ()

is -1. Opening the listener on 50070
2009-10-14 11:09:53,243 INFO org.apache.hadoop.http.HttpServer:
listener.getLocalPort() returned 50070
webServer.getConnectors()[0].getLocalPort() returned 50070

2009-10-14 11:09:53,243 INFO org.apache.hadoop.http.HttpServer: Jetty

bound to port 50070
2009-10-14 11:09:53,243 INFO org.mortbay.log: jetty-6.1.14
2009-10-14 11:09:53,433 INFO org.mortbay.log: Started
selectchannelconnec...@0.0.0.0:50070
2009-10-14 11:09:53,434 INFO
org.apache.hadoop.hdfs.server.namenode.NameNode: Web-server up at:
0.0.0.0:50070

2009-10-14 11:09:53,434 INFO org.apache.hadoop.ipc.Server: IPC Server

Responder: starting

2009-10-14 11:09:53,435 INFO org.apache.hadoop.ipc.Server: IPC Server

listener on 8020: starting