[ 
https://issues.apache.org/jira/browse/HADOOP-1865?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13168783#comment-13168783
 ] 

Joseph Shraibman commented on HADOOP-1865:
------------------------------------------

This is marked as fixed but I'm seeing it in hadoop 0.20.0

{code}
$  start-mapred.sh 
starting jobtracker, logging to 
/mnt/space/hadoop-0.22.0/bin/../logs/hadoop-hadoop-jobtracker-t.net.out
jks-desktop: starting tasktracker, logging to 
/mnt/space/hadoop-0.22.0/bin/../logs/hadoop-hadoop-tasktracker-jks-desktop.out
jks-desktop: log4j:ERROR Could not instantiate class 
[org.apache.hadoop.log.metrics.EventCounter].
jks-desktop: java.lang.ClassNotFoundException: 
org.apache.hadoop.log.metrics.EventCounter
jks-desktop:    at java.net.URLClassLoader$1.run(URLClassLoader.java:202)
jks-desktop:    at java.security.AccessController.doPrivileged(Native Method)
jks-desktop:    at java.net.URLClassLoader.findClass(URLClassLoader.java:190)
jks-desktop:    at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
jks-desktop:    at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301)
jks-desktop:    at java.lang.ClassLoader.loadClass(ClassLoader.java:247)
jks-desktop:    at java.lang.Class.forName0(Native Method)
jks-desktop:    at java.lang.Class.forName(Class.java:169)
localhost: starting tasktracker, logging to 
/mnt/space/hadoop-0.22.0/bin/../logs/hadoop-hadoop-tasktracker-t.net.out

{code}
                
> "org.apache.hadoop.metrics.jvm.EventCounter" not instantiate error
> ------------------------------------------------------------------
>
>                 Key: HADOOP-1865
>                 URL: https://issues.apache.org/jira/browse/HADOOP-1865
>             Project: Hadoop Common
>          Issue Type: Bug
>    Affects Versions: 0.13.1
>            Reporter: Yiping Han
>            Priority: Critical
>
> Hi, 
> I got the "org.apache.hadoop.metrics.jvm.EventCounter" not instantiate error. 
> This error happens for every hadoop command. But it seems it does not block 
> any operation to success. Don't know if anyone has an idea?

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to