hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hive QA (JIRA)" <>
Subject [jira] [Commented] (HIVE-19525) Spark task logs print PLAN PATH excessive number of times
Date Wed, 06 Jun 2018 02:00:00 GMT


Hive QA commented on HIVE-19525:

Here are the results of testing the latest attachment:

{color:red}ERROR:{color} -1 due to no test(s) being added or modified.

{color:green}SUCCESS:{color} +1 due to 14467 tests passed

Test results:
Console output:
Test logs:

Executing org.apache.hive.ptest.execution.TestCheckPhase
Executing org.apache.hive.ptest.execution.PrepPhase
Executing org.apache.hive.ptest.execution.YetusPhase
Executing org.apache.hive.ptest.execution.ExecutionPhase
Executing org.apache.hive.ptest.execution.ReportingPhase

This message is automatically generated.

ATTACHMENT ID: 12926235 - PreCommit-HIVE-Build

> Spark task logs print PLAN PATH excessive number of times
> ---------------------------------------------------------
>                 Key: HIVE-19525
>                 URL:
>             Project: Hive
>          Issue Type: Sub-task
>          Components: Spark
>            Reporter: Sahil Takiar
>            Assignee: Bharathkrishna Guruvayoor Murali
>            Priority: Major
>         Attachments: HIVE-19525.1.patch, HIVE-19525.2.patch
> A ton of logs with this {{Utilities - PLAN PATH = hdfs://localhost:59527/.../apache-hive/itests/qtest-spark/target/tmp/scratchdir/stakiar/6ebceb49-7a76-4159-9082-5bba44391e30/hive_2018-05-14_07-28-44_672_8205774950452575544-1/-mr-10006/bf14c0b5-a014-4ee8-8ddf-fdb7453eb0f0/map.xml}}
> Seems it print multiple times per task exception, not sure where it is coming from, but
its too verbose. It should be changed to DEBUG level. Furthermore, given that we are using
{{Utilities#getBaseWork}} anytime we need to access a {{MapWork}} or {{ReduceWork}} object,
we should make the method slightly more efficient. Right now it borrows a {{Kryo}} from a
pool and does a bunch of stuff to set the classloader, then it checks the cache to see if
the work object has already been created. It should check the cache before doing any of that.

This message was sent by Atlassian JIRA

View raw message