[jira] [Created] (HADOOP-15514) NoClassDefFoundError of TimelineCollectorManager when starting MiniCluster

2018-06-04 Thread Jeff Zhang (JIRA)
Jeff Zhang created HADOOP-15514:
---

 Summary: NoClassDefFoundError of TimelineCollectorManager when 
starting MiniCluster
 Key: HADOOP-15514
 URL: https://issues.apache.org/jira/browse/HADOOP-15514
 Project: Hadoop Common
  Issue Type: Bug
Reporter: Jeff Zhang


{code:java}
org.apache.hadoop.yarn.exceptions.YarnRuntimeException: 
java.lang.NoClassDefFoundError: 
org/apache/hadoop/yarn/server/timelineservice/collector/TimelineCollectorManager

  at java.net.URLClassLoader.findClass(URLClassLoader.java:381)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

  at java.lang.ClassLoader.defineClass1(Native Method)

  at java.lang.ClassLoader.defineClass(ClassLoader.java:763)

  at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)

  at java.net.URLClassLoader.defineClass(URLClassLoader.java:467)

  at java.net.URLClassLoader.access$100(URLClassLoader.java:73)

  at java.net.URLClassLoader$1.run(URLClassLoader.java:368)

  at java.net.URLClassLoader$1.run(URLClassLoader.java:362)

  at java.security.AccessController.doPrivileged(Native Method)

  at java.net.URLClassLoader.findClass(URLClassLoader.java:361)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:424)

  at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:349)

  at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

  at java.lang.Class.getDeclaredMethods0(Native Method)

  at java.lang.Class.privateGetDeclaredMethods(Class.java:2701)

  at java.lang.Class.getDeclaredMethods(Class.java:1975){code}
 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

-
To unsubscribe, e-mail: common-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org



[jira] [Created] (HADOOP-12028) Allow to set handler thread name when building IPC Server

2015-05-24 Thread Jeff Zhang (JIRA)
Jeff Zhang created HADOOP-12028:
---

 Summary: Allow to set handler thread name when building IPC Server
 Key: HADOOP-12028
 URL: https://issues.apache.org/jira/browse/HADOOP-12028
 Project: Hadoop Common
  Issue Type: Improvement
Affects Versions: 2.7.0
Reporter: Jeff Zhang


Currently IPC use the server port to differentiate it with other IPC server. 
This is not very clear especially when port is randomly generated. It is better 
to set the server name when building the server and use the server name  as the 
part of handler thread name 
{code}
2015-05-25 10:43:40,181 INFO  [IPC Server handler 0 on 58849] 
history.HistoryEventHandler (HistoryEventHandler.java:handleCriticalEvent(110)) 
- [HISTORY][DAG:dag_1432521818638_0001_1][Event:DAG_SUBMITTED]: 
dagID=dag_1432521818638_0001_1, submitTime=1432521820100
2015-05-25 10:43:40,200 INFO  [IPC Server handler 0 on 58849] impl.DAGImpl 
(DAGImpl.java:assignDAGScheduler(1360)) - Using DAG Scheduler: 
org.apache.tez.dag.app.dag.impl.DAGSchedulerNaturalOrderControlled
2015-05-25 10:43:40,201 INFO  [IPC Server handler 0 on 58849] h
{code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)