hudi-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Feichi Feng (Jira)" <>
Subject [jira] [Commented] (HUDI-724) Parallelize GetSmallFiles For Partitions
Date Fri, 20 Mar 2020 17:23:00 GMT


Feichi Feng commented on HUDI-724:

Hi all, regarding to the question why timeline server is not helping:

in my prototype, it's a single spark job, within the spark job, it first does inserts, then
deletes the old version of the data(due to data modeling, the new records and old records
are under different Primary Keys). 

so when the spark app starts, it first try to do inserts, while nothing is in the timeline
server yet. for the inserts, it go through the code path to getSmallFiles in the non-parallelized
for-loop, which this PR is trying to improve. Maybe it's due to that the writes are inserts
only, so it didn't go through the code path for "bloom index lookup and populate small files
to timeline server".  

However, with embed timeline server on, the following delete operations ran faster, since
at that time, the timeline server already have caches that's stored by the insert operation. 

> Parallelize GetSmallFiles For Partitions
> ----------------------------------------
>                 Key: HUDI-724
>                 URL:
>             Project: Apache Hudi (incubating)
>          Issue Type: Improvement
>          Components: Performance, Writer Core
>            Reporter: Feichi Feng
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: gap.png, nogapAfterImprovement.png
>   Original Estimate: 48h
>          Time Spent: 10m
>  Remaining Estimate: 47h 50m
> When writing data, a gap was observed between spark stages. By tracking down where the
time was spent on the spark driver, it's get-small-files operation for partitions.
> When creating the UpsertPartitioner and trying to assign insert records, it uses a normal
for-loop for get the list of small files for all partitions that the load is going to load
data to, and the process is very slow when there are a lot of partitions to go through. While
the operation is running on spark driver process, all other worker nodes are sitting idle
waiting for tasks.
> For all those partitions, they don't affect each other, so the get-small-files operations
can be parallelized. The change I made is to pass the JavaSparkContext to the UpsertPartitioner,
and create RDD for the partitions and eventually send the get small files operations to multiple
> screenshot attached for 
> the gap without the improvement
> the spark stage with the improvement (no gap)

This message was sent by Atlassian Jira

View raw message