hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "stack (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-9829) make the compaction logging less confusing
Date Fri, 06 Dec 2013 22:11:35 GMT

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

stack commented on HBASE-9829:
------------------------------

Fine by me Sergey.  You can address on commit.   Above are just nits.  Patch is nice.

> make the compaction logging less confusing
> ------------------------------------------
>
>                 Key: HBASE-9829
>                 URL: https://issues.apache.org/jira/browse/HBASE-9829
>             Project: HBase
>          Issue Type: Improvement
>          Components: Compaction
>            Reporter: Sergey Shelukhin
>            Assignee: Sergey Shelukhin
>            Priority: Minor
>         Attachments: HBASE-9829.patch
>
>
> 1) One of the most popular question from HBase users has got to be "I have scheduled
major compactions to run once per week, why are there so many".
> We need to somehow tell the user, wherever we log that there is a "major" compaction,
whether it's a major compaction because that's what was in the request (from regular major
compaction or user request), or was it just promoted because it took all files. Esp. the latter
should be clear.
> 2) small vs large compaction threads and minor vs major compactions is confusing. Maybe
the threads can be named short and long compactions.
> We



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message