[
https://issues.apache.org/jira/browse/ACCUMULO-4187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15238543#comment-15238543
]
ASF GitHub Bot commented on ACCUMULO-4187:
------------------------------------------
Github user joshelser commented on a diff in the pull request:
https://github.com/apache/accumulo/pull/90#discussion_r59489093
--- Diff: core/src/main/java/org/apache/accumulo/core/conf/Property.java ---
@@ -293,6 +293,8 @@
"The maximum number of concurrent tablet migrations for a tablet
server"),
TSERV_MAJC_MAXCONCURRENT("tserver.compaction.major.concurrent.max", "3",
PropertyType.COUNT,
"The maximum number of concurrent major compactions for a tablet
server"),
+ TSERV_MAJC_THROUGHPUT("tserver.compaction.major.throughput", "0B",
PropertyType.MEMORY,
+ "Maximum number of bytes to read or write per second over all major
compactions, or 0 for unlimited."),
--- End diff --
".... in a TabletServer." Clarify that this is not global, but local to a
tserver.
> Rate limiting of major compactions
> ----------------------------------
>
> Key: ACCUMULO-4187
> URL: https://issues.apache.org/jira/browse/ACCUMULO-4187
> Project: Accumulo
> Issue Type: Improvement
> Components: core, tserver
> Affects Versions: 1.8.0
> Reporter: Shawn Walker
> Assignee: Shawn Walker
> Priority: Minor
> Fix For: 1.8.0
>
>
> In discussing [ACCUMULO-4166] with Keith Turner, we decided that the
> underlying issue is that major compactions can overwhelm a tablet server,
> rendering it nearly unresponsive.
> To address this, we should take a cue from Apache Cassandra and restrict how
> quickly we perform major compactions. Rate limiting reads and writes
> involved in major compactions will directly affect the IO load caused by
> major compactions, and should also indirectly affect the CPU load.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
