hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Hudson (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-15808) Reduce potential bulk load intermediate space usage and waste
Date Fri, 27 May 2016 17:44:13 GMT

    [ https://issues.apache.org/jira/browse/HBASE-15808?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15304433#comment-15304433
] 

Hudson commented on HBASE-15808:
--------------------------------

FAILURE: Integrated in HBase-0.98-matrix #348 (See [https://builds.apache.org/job/HBase-0.98-matrix/348/])
HBASE-15808 Reduce potential bulk load intermediate space usage and (apurtell: rev a38b633a4bdf171d9a12a600a9b1a22b1f09dec9)
* hbase-server/src/test/java/org/apache/hadoop/hbase/mapreduce/TestLoadIncrementalHFilesSplitRecovery.java
* hbase-server/src/main/java/org/apache/hadoop/hbase/mapreduce/LoadIncrementalHFiles.java


> Reduce potential bulk load intermediate space usage and waste
> -------------------------------------------------------------
>
>                 Key: HBASE-15808
>                 URL: https://issues.apache.org/jira/browse/HBASE-15808
>             Project: HBase
>          Issue Type: Improvement
>    Affects Versions: 1.2.0
>            Reporter: Jerry He
>            Assignee: Jerry He
>            Priority: Minor
>             Fix For: 2.0.0, 1.3.0, 1.4.0, 1.2.2, 0.98.20
>
>         Attachments: HBASE-15808-v2.patch, HBASE-15808-v3.patch, HBASE-15808.patch
>
>
> If the bulk load input files do not match the existing region boudaries, the files will
be splitted.
> In the unfornate cases where the files need to be splitted multiple times,
> the process can consume unnecessary space and can even cause out of space.
> Here is over-simplified example.
> Orinal size of input files:  
>   consumed space: size --> 300GB
> After a round of splits: 
>   consumed space: size + tmpspace1 --> 300GB + 300GB
> After another round of splits: 
>   consumded space:  size + tmpspace1 + tmpspace2 --> 300GB + 300GB + 300GB
> ..
> Currently we don't do any cleanup in the process. At least all the intermediate tmpspace
(not the last one) can be deleted in the process.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message