hive-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jason Dere (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HIVE-16282) Semijoin: Disable slow-start for the bloom filter aggregate task
Date Sat, 25 Mar 2017 20:49:41 GMT

     [ https://issues.apache.org/jira/browse/HIVE-16282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Jason Dere updated HIVE-16282:
------------------------------
       Resolution: Fixed
    Fix Version/s: 2.2.0
           Status: Resolved  (was: Patch Available)

committed to master

> Semijoin: Disable slow-start for the bloom filter aggregate task
> ----------------------------------------------------------------
>
>                 Key: HIVE-16282
>                 URL: https://issues.apache.org/jira/browse/HIVE-16282
>             Project: Hive
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>            Reporter: Gopal V
>            Assignee: Deepak Jaiswal
>             Fix For: 2.2.0
>
>         Attachments: extended plan.rtf, HIVE-16282.1.patch, HIVE-16282.2.patch, HIVE-16282.3.patch,
HIVE-16282.4.patch, HIVE-16282.5.patch
>
>
> The slow-start of the bloom filter vertex is a scheduling problem which causes more pre-emption
than is useful.
> When the bloom filters are arranged as follows
> Map 1(10 tasks)->Reducer 2(1 task)->Map 3(100 tasks)
> Map 3 and Map 1 are immediately active since Reducer 2 -> Map 3 is a broadcast edge.
> Once 3 tasks in Map 1 finish, the engine kills one active task from Map 3 to make room
for Reducer 2.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Mime
View raw message