You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hive.apache.org by "ASF GitHub Bot (Jira)" <ji...@apache.org> on 2022/05/12 14:23:00 UTC
[jira] [Work logged] (HIVE-25335) Unreasonable setting reduce number, when join big size table(but small row count) and small size table
[ https://issues.apache.org/jira/browse/HIVE-25335?focusedWorklogId=769681&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-769681 ]
ASF GitHub Bot logged work on HIVE-25335:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 12/May/22 14:22
Start Date: 12/May/22 14:22
Worklog Time Spent: 10m
Work Description: zabetak commented on PR #2490:
URL: https://github.com/apache/hive/pull/2490#issuecomment-1125059076
@zhengchenyu I don't think it's possible to reopen a closed PR. You can create a new one instead.
Issue Time Tracking
-------------------
Worklog Id: (was: 769681)
Time Spent: 2.5h (was: 2h 20m)
> Unreasonable setting reduce number, when join big size table(but small row count) and small size table
> ------------------------------------------------------------------------------------------------------
>
> Key: HIVE-25335
> URL: https://issues.apache.org/jira/browse/HIVE-25335
> Project: Hive
> Issue Type: Improvement
> Reporter: zhengchenyu
> Assignee: zhengchenyu
> Priority: Major
> Labels: pull-request-available
> Attachments: HIVE-25335.001.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> I found an application which is slow in our cluster, because the proccess bytes of one reduce is very huge, but only two reduce.
> when I debug, I found the reason. Because in this sql, one big size table (about 30G) with few row count(about 3.5M), another small size table (about 100M) have more row count (about 3.6M). So JoinStatsRule.process only use 100M to estimate reducer's number. But we need to process 30G byte in fact.
--
This message was sent by Atlassian Jira
(v8.20.7#820007)