[jira] [Updated] (HBASE-9829) make the compaction logging less confusing

["Sergey Shelukhin (JIRA)" <ji...@apache.org>]

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

Sergey Shelukhin updated HBASE-9829:
------------------------------------

    Description: 
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

  was:
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, when we log 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


> 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
>            Priority: Minor
>
> 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)