[
https://issues.apache.org/jira/browse/HBASE-8617?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13689174#comment-13689174
]
Hudson commented on HBASE-8617:
-------------------------------
Integrated in hbase-0.95-on-hadoop2 #139 (See
[https://builds.apache.org/job/hbase-0.95-on-hadoop2/139/])
HBASE-8617: Introducing a new config to disable writes during recovering
(Revision 1494814)
Result = FAILURE
jeffreyz :
Files :
*
/hbase/branches/0.95/hbase-common/src/main/java/org/apache/hadoop/hbase/HConstants.java
*
/hbase/branches/0.95/hbase-server/src/main/java/org/apache/hadoop/hbase/regionserver/HRegion.java
*
/hbase/branches/0.95/hbase-server/src/test/java/org/apache/hadoop/hbase/master/TestDistributedLogSplitting.java
> Introducing a new config to disable writes during recovering
> -------------------------------------------------------------
>
> Key: HBASE-8617
> URL: https://issues.apache.org/jira/browse/HBASE-8617
> Project: HBase
> Issue Type: Improvement
> Components: regionserver
> Affects Versions: 0.98.0, 0.95.1
> Reporter: Jeffrey Zhong
> Assignee: Jeffrey Zhong
> Fix For: 0.98.0, 0.95.2
>
> Attachments: HBASE-8617.patch, HBASE-8617-v2.patch,
> hbase-8617-v3.patch
>
>
> In distributedLogReplay(hbase-7006), we allow writes even when a region is in
> recovering. It may cause undesired behavior when applications(or deployments)
> already are near its write capacity because distributedLogReplay generates
> more write traffic to remaining region servers.
> The new config "hbase.regionserver.disallow.writes.when.recovering" tries to
> address the above situation so that recovering won't be affected by
> application normal write traffic.
> The default value of this config is false(meaning allow writes in recovery)
--
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
