You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "Deepak Jaiswal (JIRA)" <ji...@apache.org> on 2018/04/15 20:50:00 UTC
[jira] [Updated] (HIVE-19195) .testCliDriver[auto_sortmerge_join_2]
is flaky
[ https://issues.apache.org/jira/browse/HIVE-19195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepak Jaiswal updated HIVE-19195:
----------------------------------
Attachment: HIVE-19195.1.patch
> .testCliDriver[auto_sortmerge_join_2] is flaky
> ----------------------------------------------
>
> Key: HIVE-19195
> URL: https://issues.apache.org/jira/browse/HIVE-19195
> Project: Hive
> Issue Type: Sub-task
> Components: Test
> Reporter: Ashutosh Chauhan
> Assignee: Deepak Jaiswal
> Priority: Major
> Attachments: HIVE-19195.1.patch
>
>
> This test is certainly flaky. Seems like it makes some assumption about available memory. Consider dropping this altogether.
> {code}
> Client Execution succeeded but contained differences (error code = 1) after executing auto_sortmerge_join_2.q
> 1101,1103d1100
> < Hive Runtime Error: Map local work exhausted memory
> < FAILED: Execution Error, return code 3 from org.apache.hadoop.hive.ql.exec.mr.MapredLocalTask
> < ATTEMPT: Execute BackupTask: org.apache.hadoop.hive.ql.exec.mr.MapRedTask
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)