[
https://issues.apache.org/jira/browse/HIVE-25335?focusedWorklogId=794663&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-794663
]
ASF GitHub Bot logged work on HIVE-25335:
-----------------------------------------
Author: ASF GitHub Bot
Created on: 25/Jul/22 00:23
Start Date: 25/Jul/22 00:23
Worklog Time Spent: 10m
Work Description: github-actions[bot] commented on PR #3292:
URL: https://github.com/apache/hive/pull/3292#issuecomment-1193429305
This pull request has been automatically marked as stale because it has not
had recent activity. It will be closed if no further activity occurs.
Feel free to reach out on the d...@hive.apache.org list if the patch is in
need of reviews.
Issue Time Tracking
-------------------
Worklog Id: (was: 794663)
Time Spent: 3.5h (was: 3h 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: 3.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.10#820010)
