Hello Peter For the history logging exception, would you mind filing a jira for this issue ( https://issues.apache.org/jira/browse/TEZ ) and attach the yarn applications log obtained by running the “yarn logs -applicationId” command?
The history logging happens on a separate thread and its exception should not cause any fatal errors. The query hanging might be due to a different issue. thanks — Hitesh On Jan 15, 2015, at 7:44 AM, peterm_second <regest...@gmail.com> wrote: > Hi Guys, > I am running a docker based hadoop cluster, with hive 0.14 and tez 0.6 > I've had successfully managed to make my setup work before, I've increased > the input data to my jobs and now I get this exception : > > 2015-01-15 14:56:32,872 ERROR [HistoryEventHandlingThread] > yarn.YarnUncaughtExceptionHandler: Thread > Thread[HistoryEventHandlingThread,5,main] threw an Exception. > java.util.ConcurrentModificationException > at java.util.Hashtable$Enumerator.next(Hashtable.java:1367) > at > org.apache.hadoop.conf.Configuration.iterator(Configuration.java:2144) > at > org.apache.tez.dag.history.utils.DAGUtils.convertConfigurationToATSMap(DAGUtils.java:365) > at > org.apache.tez.dag.history.logging.impl.HistoryEventJsonConversion.convertAppLaunchedEvent(HistoryEventJsonConversion.java:139) > at > org.apache.tez.dag.history.logging.impl.HistoryEventJsonConversion.convertToJson(HistoryEventJsonConversion.java:64) > at > org.apache.tez.dag.history.logging.impl.SimpleHistoryLoggingService.handleEvent(SimpleHistoryLoggingService.java:154) > at > org.apache.tez.dag.history.logging.impl.SimpleHistoryLoggingService.access$300(SimpleHistoryLoggingService.java:38) > at > org.apache.tez.dag.history.logging.impl.SimpleHistoryLoggingService$1.run(SimpleHistoryLoggingService.java:108) > at java.lang.Thread.run(Thread.java:745) > > > Which frustrates me to no end, what could possibly be happening that would > cause a ConcurentModificationException. > > The sql I am running is > select > pdepartment.PdDepartment , incidents.DayOfWeek , category.Category , > count(incidents.incidntNum) NumberOfIncidents > > from > incidents > JOIN category ON ( category.key = incidents.Category_Id ) > JOIN pdepartment ON ( pdepartment.key = incidents.PdDistrict_Id ) > > group by pdepartment.PdDepartment, incidents.DayOfWeek, category.Category > with cube > > As I said I am certain that my set up works, I've changed nothing and I get > only this one exception in the logs, and that's in the yarn log. The mr job > logs are clean. The tez hadoop app isn't failing it just hangs. > > Have you guys seen anything like that before? Any ideas what might the > problem be ? I'd love any suggestion cause I am out of ideas. > > Thanks, > Peter
