[
https://issues.apache.org/jira/browse/HADOOP-1937?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12532575
]
Hadoop QA commented on HADOOP-1937:
-----------------------------------
+1 overall. Here are the results of testing the latest attachment
http://issues.apache.org/jira/secure/attachment/12367125/patch.txt
against trunk revision r582066.
@author +1. The patch does not contain any @author tags.
javadoc +1. The javadoc tool did not generate any warning messages.
javac +1. The applied patch does not generate any new compiler warnings.
findbugs +1. The patch does not introduce any new Findbugs warnings.
core tests +1. The patch passed core unit tests.
contrib tests +1. The patch passed contrib unit tests.
Test results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/891/testReport/
Findbugs warnings:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/891/artifact/trunk/build/test/findbugs/newPatchFindbugsWarnings.html
Checkstyle results:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/891/artifact/trunk/build/test/checkstyle-errors.html
Console output:
http://lucene.zones.apache.org:8080/hudson/job/Hadoop-Patch/891/console
This message is automatically generated.
> [hbase] when the master times out a region server's lease, it is too
> aggressive in reclaiming the server's log
> --------------------------------------------------------------------------------------------------------------
>
> Key: HADOOP-1937
> URL: https://issues.apache.org/jira/browse/HADOOP-1937
> Project: Hadoop
> Issue Type: Bug
> Components: contrib/hbase
> Affects Versions: 0.15.0
> Reporter: Jim Kellerman
> Assignee: Jim Kellerman
> Fix For: 0.15.0
>
> Attachments: patch.txt
>
>
> When a region server's lease times out, the master immediately begins trying
> to split the server's log file. There have been cases where a region server
> was just a little late reporting to the master and the master had already
> started trying to reclaim the server's log, even though the server was still
> writing to it.
> There needs to be some kind of "grace period" in which, if the region server
> reports in, the master re-instates the server. If the "grace period" expires,
> then the master should start processing the server's log.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
