hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sergey Shelukhin (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-8652) Number of compacting KVs is not reset at the end of compaction
Date Thu, 30 May 2013 18:01:26 GMT

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

Sergey Shelukhin commented on HBASE-8652:
-----------------------------------------

compaction uses current progress until the next compaction, at which point it is reset, so
totalCompactingKVs as well as current are reset implicitly. What I wonder about is how did
this ever work with parallel compactions, which are possible. Perhaps progress should be moved
to CompactionContext object.
                
> Number of compacting KVs is not reset at the end of compaction
> --------------------------------------------------------------
>
>                 Key: HBASE-8652
>                 URL: https://issues.apache.org/jira/browse/HBASE-8652
>             Project: HBase
>          Issue Type: Bug
>            Reporter: Ted Yu
>            Priority: Minor
>
> Looking at master:60010/master-status#compactStas , I noticed that 'Num. Compacting KVs'
column stays unchanged at non-zero value(s).
> In DefaultCompactor#compact(), we have this at the beginning:
> {code}
>     this.progress = new CompactionProgress(fd.maxKeyCount);
> {code}
> But progress.totalCompactingKVs is not reset at the end of compact().

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Mime
View raw message