accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Keith Turner (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (ACCUMULO-3944) Tablet attempts to split or major compact after every bulk file import
Date Fri, 24 Jul 2015 21:53:05 GMT

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

Keith Turner commented on ACCUMULO-3944:
----------------------------------------

I think I added this in ACCUMULO-514 when I noticed the system doing nothing for a bit of
time when there was work to be done. 

I think the checks are usually just against in memory data structs and very quick (there may
be cases where the checks go to hdfs).   Were you seeing performance problems with this code?

> Tablet attempts to split or major compact after every bulk file import
> ----------------------------------------------------------------------
>
>                 Key: ACCUMULO-3944
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-3944
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: tserver
>            Reporter: Eric Newton
>            Priority: Blocker
>             Fix For: 1.8.0
>
>
> I noticed this bit of code in tablet, after it has bulk imported a file, but before the
bulk import is finished:
> {code}
>       if (needsSplit()) {
>         getTabletServer().executeSplit(this);
>       } else {
>         initiateMajorCompaction(MajorCompactionReason.NORMAL);
>       }
> {code}
> I'm pretty sure we can leave this to the normal tablet server mechanism for deciding
when to split or compact.



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

Mime
View raw message