[
https://issues.apache.org/jira/browse/HBASE-9904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13815169#comment-13815169
]
Hadoop QA commented on HBASE-9904:
----------------------------------
{color:red}-1 overall{color}. Here are the results of testing the latest
attachment
http://issues.apache.org/jira/secure/attachment/12612417/scan.diff
against trunk revision .
{color:green}+1 @author{color}. The patch does not contain any @author
tags.
{color:green}+1 tests included{color}. The patch appears to include 9 new
or modified tests.
{color:red}-1 patch{color}. The patch command could not apply the patch.
Console output:
https://builds.apache.org/job/PreCommit-HBASE-Build/7758//console
This message is automatically generated.
> Solve skipping data in HTable scans
> -----------------------------------
>
> Key: HBASE-9904
> URL: https://issues.apache.org/jira/browse/HBASE-9904
> Project: HBase
> Issue Type: Bug
> Components: Client
> Affects Versions: 0.89-fb
> Reporter: Manukranth Kolloju
> Fix For: 0.89-fb
>
> Attachments: scan.diff
>
>
> The HTable client cannot retry a scan operation in the
> getRegionServerWithRetries code path.
> This will result in the client missing data. This can be worked around using
> hbase.client.retries.number to 1.
> The whole problem is that Callable knows nothing about retries and the
> protocol it dances to as well doesn't support retires.
> This fix will keep Callable protocol (ugly thing worth merciless refactoring)
> intact but will change
> ScannerCallable to anticipate retries. What we want is to make failed
> operations to be identities for outside world:
> N1 , N2 , F3 , N3 , F4 , F4 , N4 ... = N1 , N2 , N3 , N4 ...
> where Nk are successful operation and Fk are failed operations.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
