You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@hive.apache.org by Echo Li <ec...@gmail.com> on 2014/10/04 01:51:42 UTC
Tez Vertex failure
Hi guys,
I run some simple hive query and got the error below:
Status: Running (application id: application_1412033199033_6623)
Map 1: -/- Reducer 2: 0/1
Status: Failed
Vertex failed, vertexName=Map 1, vertexId=vertex_1412033199033_6623_1_01,
diagnostics=[Vertex Input: visit initializer failed., serious problem]
Vertex killed, vertexName=Reducer 2,
vertexId=vertex_1412033199033_6623_1_00, diagnostics=[Vertex received Kill
in INITED state.]
DAG failed due to vertex failure. failedVertices:1 killedVertices:1
FAILED: Execution Error, return code 2 from
org.apache.hadoop.hive.ql.exec.tez.TezTask
Any idea what's the cause and what's the fix? I suspect its some sort data
issue as it only happens to certain partitions, anybody had any experience
on this?
Thanks guys.
Re: Tez Vertex failure
Posted by karthik Srivasthava <ka...@gmail.com>.
Is ur Query working when you set hive.execution.engine=mr..?
On Fri, Oct 3, 2014 at 7:20 PM, Echo Li <ec...@gmail.com> wrote:
> thanks for reply!
>
> the query is: *select count(customerid) from tableName where ymd=20140930
> ;*
>
> when I try to get the application logs only got this:
>
>
>
>
>
>
>
>
>
>
> *dag_1412033199033_6639_1.dot : Total file length is 1562 bytes.stderr :
> Total file length is 0 bytes.stderr_dag_1412033199033_6639_1 : Total file
> length is 0 bytes.stderr_dag_1412033199033_6639_1_post : Total file length
> is 0 bytes.stdout : Total file length is 0
> bytes.stdout_dag_1412033199033_6639_1 : Total file length is 0
> bytes.stdout_dag_1412033199033_6639_1_post : Total file length is 0
> bytes.syslog : Total file length is 7436
> bytes.syslog_dag_1412033199033_6639_1 : Total file length is 14695
> bytes.syslog_dag_1412033199033_6639_1_post : Total file length is 136
> bytes.*
>
> Also when I run this query: select * from visit where ymd=20140930 limit
> 10;
> got error:
> *Failed with exception java.io.IOException:java.lang.RuntimeException:
> serious problem*
> The table is ORC format, in google cloud storage.
>
>
> On Fri, Oct 3, 2014 at 4:54 PM, Vikram Dixit <vi...@hortonworks.com>
> wrote:
>
>> Hi,
>>
>> Can you share the query and the application logs with us? Which
>> version of hive is this?
>>
>> Thanks
>> Vikram.
>>
>> On Fri, Oct 3, 2014 at 4:51 PM, Echo Li <ec...@gmail.com> wrote:
>> > Hi guys,
>> >
>> > I run some simple hive query and got the error below:
>> >
>> > Status: Running (application id: application_1412033199033_6623)
>> >
>> > Map 1: -/- Reducer 2: 0/1
>> > Status: Failed
>> > Vertex failed, vertexName=Map 1,
>> vertexId=vertex_1412033199033_6623_1_01,
>> > diagnostics=[Vertex Input: visit initializer failed., serious problem]
>> > Vertex killed, vertexName=Reducer 2,
>> > vertexId=vertex_1412033199033_6623_1_00, diagnostics=[Vertex received
>> Kill
>> > in INITED state.]
>> > DAG failed due to vertex failure. failedVertices:1 killedVertices:1
>> > FAILED: Execution Error, return code 2 from
>> > org.apache.hadoop.hive.ql.exec.tez.TezTask
>> >
>> >
>> > Any idea what's the cause and what's the fix? I suspect its some sort
>> data
>> > issue as it only happens to certain partitions, anybody had any
>> experience
>> > on this?
>> >
>> > Thanks guys.
>> >
>> >
>>
>> --
>> CONFIDENTIALITY NOTICE
>> NOTICE: This message is intended for the use of the individual or entity
>> to
>> which it is addressed and may contain information that is confidential,
>> privileged and exempt from disclosure under applicable law. If the reader
>> of this message is not the intended recipient, you are hereby notified
>> that
>> any printing, copying, dissemination, distribution, disclosure or
>> forwarding of this communication is strictly prohibited. If you have
>> received this communication in error, please contact the sender
>> immediately
>> and delete it from your system. Thank You.
>>
>
>
Re: Tez Vertex failure
Posted by Echo Li <ec...@gmail.com>.
thanks for reply!
the query is: *select count(customerid) from tableName where ymd=20140930 ;*
when I try to get the application logs only got this:
*dag_1412033199033_6639_1.dot : Total file length is 1562 bytes.stderr :
Total file length is 0 bytes.stderr_dag_1412033199033_6639_1 : Total file
length is 0 bytes.stderr_dag_1412033199033_6639_1_post : Total file length
is 0 bytes.stdout : Total file length is 0
bytes.stdout_dag_1412033199033_6639_1 : Total file length is 0
bytes.stdout_dag_1412033199033_6639_1_post : Total file length is 0
bytes.syslog : Total file length is 7436
bytes.syslog_dag_1412033199033_6639_1 : Total file length is 14695
bytes.syslog_dag_1412033199033_6639_1_post : Total file length is 136
bytes.*
Also when I run this query: select * from visit where ymd=20140930 limit 10;
got error:
*Failed with exception java.io.IOException:java.lang.RuntimeException:
serious problem*
The table is ORC format, in google cloud storage.
On Fri, Oct 3, 2014 at 4:54 PM, Vikram Dixit <vi...@hortonworks.com> wrote:
> Hi,
>
> Can you share the query and the application logs with us? Which
> version of hive is this?
>
> Thanks
> Vikram.
>
> On Fri, Oct 3, 2014 at 4:51 PM, Echo Li <ec...@gmail.com> wrote:
> > Hi guys,
> >
> > I run some simple hive query and got the error below:
> >
> > Status: Running (application id: application_1412033199033_6623)
> >
> > Map 1: -/- Reducer 2: 0/1
> > Status: Failed
> > Vertex failed, vertexName=Map 1, vertexId=vertex_1412033199033_6623_1_01,
> > diagnostics=[Vertex Input: visit initializer failed., serious problem]
> > Vertex killed, vertexName=Reducer 2,
> > vertexId=vertex_1412033199033_6623_1_00, diagnostics=[Vertex received
> Kill
> > in INITED state.]
> > DAG failed due to vertex failure. failedVertices:1 killedVertices:1
> > FAILED: Execution Error, return code 2 from
> > org.apache.hadoop.hive.ql.exec.tez.TezTask
> >
> >
> > Any idea what's the cause and what's the fix? I suspect its some sort
> data
> > issue as it only happens to certain partitions, anybody had any
> experience
> > on this?
> >
> > Thanks guys.
> >
> >
>
> --
> CONFIDENTIALITY NOTICE
> NOTICE: This message is intended for the use of the individual or entity to
> which it is addressed and may contain information that is confidential,
> privileged and exempt from disclosure under applicable law. If the reader
> of this message is not the intended recipient, you are hereby notified that
> any printing, copying, dissemination, distribution, disclosure or
> forwarding of this communication is strictly prohibited. If you have
> received this communication in error, please contact the sender immediately
> and delete it from your system. Thank You.
>
Re: Tez Vertex failure
Posted by Vikram Dixit <vi...@hortonworks.com>.
Hi,
Can you share the query and the application logs with us? Which
version of hive is this?
Thanks
Vikram.
On Fri, Oct 3, 2014 at 4:51 PM, Echo Li <ec...@gmail.com> wrote:
> Hi guys,
>
> I run some simple hive query and got the error below:
>
> Status: Running (application id: application_1412033199033_6623)
>
> Map 1: -/- Reducer 2: 0/1
> Status: Failed
> Vertex failed, vertexName=Map 1, vertexId=vertex_1412033199033_6623_1_01,
> diagnostics=[Vertex Input: visit initializer failed., serious problem]
> Vertex killed, vertexName=Reducer 2,
> vertexId=vertex_1412033199033_6623_1_00, diagnostics=[Vertex received Kill
> in INITED state.]
> DAG failed due to vertex failure. failedVertices:1 killedVertices:1
> FAILED: Execution Error, return code 2 from
> org.apache.hadoop.hive.ql.exec.tez.TezTask
>
>
> Any idea what's the cause and what's the fix? I suspect its some sort data
> issue as it only happens to certain partitions, anybody had any experience
> on this?
>
> Thanks guys.
>
>
--
CONFIDENTIALITY NOTICE
NOTICE: This message is intended for the use of the individual or entity to
which it is addressed and may contain information that is confidential,
privileged and exempt from disclosure under applicable law. If the reader
of this message is not the intended recipient, you are hereby notified that
any printing, copying, dissemination, distribution, disclosure or
forwarding of this communication is strictly prohibited. If you have
received this communication in error, please contact the sender immediately
and delete it from your system. Thank You.