You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hive.apache.org by "Gopal V (JIRA)" <ji...@apache.org> on 2015/03/16 16:05:38 UTC
[jira] [Created] (HIVE-9976) Possible race condition in
DynamicPartitionPruner for <200ms tasks
Gopal V created HIVE-9976:
-----------------------------
Summary: Possible race condition in DynamicPartitionPruner for <200ms tasks
Key: HIVE-9976
URL: https://issues.apache.org/jira/browse/HIVE-9976
Project: Hive
Issue Type: Bug
Components: Tez
Affects Versions: llap
Reporter: Gopal V
Assignee: Gunther Hagleitner
Race condition in the DynamicPartitionPruner between DynamicPartitionPruner::processVertex() and DynamicPartitionpruner::addEvent() for tasks which respond with both the result and success in a single heartbeat sequence.
{code}
2015-03-16 07:05:01,589 ERROR [InputInitializer [Map 1] #0] tez.DynamicPartitionPruner: Expecting: 1, received: 0
2015-03-16 07:05:01,590 ERROR [Dispatcher thread: Central] impl.VertexImpl: Vertex Input: store_sales initializer failed, vertex=vertex_1424502260528_1113_4_04 [Map 1]
org.apache.tez.dag.app.dag.impl.AMUserCodeException: org.apache.hadoop.hive.ql.metadata.HiveException: Incorrect event count in dynamic parition pruning
{code}
All 4 upstream vertices of Map 1 need to finish within ~200ms to trigger this, which seems to be happening with LLAP.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)