Return-Path: X-Original-To: apmail-hive-user-archive@www.apache.org Delivered-To: apmail-hive-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 98CE910872 for ; Thu, 15 Jan 2015 15:45:55 +0000 (UTC) Received: (qmail 23248 invoked by uid 500); 15 Jan 2015 15:45:55 -0000 Delivered-To: apmail-hive-user-archive@hive.apache.org Received: (qmail 23188 invoked by uid 500); 15 Jan 2015 15:45:55 -0000 Mailing-List: contact user-help@hive.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: user@hive.apache.org Delivered-To: mailing list user@hive.apache.org Received: (qmail 23177 invoked by uid 99); 15 Jan 2015 15:45:55 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2015 15:45:55 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of regestrer@gmail.com designates 74.125.82.169 as permitted sender) Received: from [74.125.82.169] (HELO mail-we0-f169.google.com) (74.125.82.169) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 15 Jan 2015 15:45:28 +0000 Received: by mail-we0-f169.google.com with SMTP id m14so15467259wev.0 for ; Thu, 15 Jan 2015 07:44:42 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:subject :content-type; bh=jGrsoN8nuqvuCNsyBQEGk55xM0qhdVRdtCBtMGFj/N0=; b=naJioACXSb/GrotaACC+5Di7TFs1VEnsBxjpsNCrgUHxmdnEWdqIJWZm3r1p7K6Dxt hFi9a+ad7m/w1j42Hsq/z0AcE8fSdt/UHCNglmeZpmiOg57JEyUQC7EWJwPfer4N8Gly 8x2HIZUns5ukVo1a/hQWNI2AcPmx4y2gK3BR/hRlgYmjQZ7RJjoic2FKU13dq4k1WNio KJGUjUxlbA3yvqnGl9RN1lkdZ3QER3102ZeSKTm5PI1xTZZE0tK5zypbXoUy3eicPe07 u+BLrG3806Xg37GGiIs8+rvwr74mIK9PNzPH9t7rZbale5MR3d0GHWtCmi6nt3LzPe+A 7TtA== X-Received: by 10.194.203.199 with SMTP id ks7mr18892455wjc.105.1421336682288; Thu, 15 Jan 2015 07:44:42 -0800 (PST) Received: from [172.20.20.66] ([77.70.78.3]) by mx.google.com with ESMTPSA id o1sm2527044wjf.41.2015.01.15.07.44.40 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 15 Jan 2015 07:44:41 -0800 (PST) Message-ID: <54B7E070.10808@gmail.com> Date: Thu, 15 Jan 2015 17:44:48 +0200 From: peterm_second User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: "user@tez.apache.org" , "user@hive.apache.org" Subject: Tez Hive Job failing during initialization Content-Type: multipart/alternative; boundary="------------020705090209010106020702" X-Virus-Checked: Checked by ClamAV on apache.org This is a multi-part message in MIME format. --------------020705090209010106020702 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit 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 --------------020705090209010106020702 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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
--------------020705090209010106020702--