[
https://issues.apache.org/jira/browse/HBASE-12448?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14203175#comment-14203175
]
Lars Hofhansl commented on HBASE-12448:
---------------------------------------
Technically bytesWritten would not need to be a long, as it is limited by the
external setting (and making it so large would defeat the purpose). :) Still
better to change it.
+1
(In a followup jira we should rationalize the two things together. For example,
say a compaction is really slow at the HDFS level, then checking every 10mb
whether the region is closed is too slow).
> Fix rate reporting in compaction progress DEBUG logging
> -------------------------------------------------------
>
> Key: HBASE-12448
> URL: https://issues.apache.org/jira/browse/HBASE-12448
> Project: HBase
> Issue Type: Bug
> Reporter: Andrew Purtell
> Assignee: Andrew Purtell
> Fix For: 2.0.0, 0.98.8, 0.99.2
>
> Attachments: HBASE-12448-0.98.patch, HBASE-12448-0.98.patch,
> HBASE-12448.patch, HBASE-12448.patch
>
>
> HBASE-11702 introduced rate reporting at DEBUG level for long running
> compactions but failed to align bytesWritten with the reporting interval.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
