Mailing-List: contact hbase-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hbase-dev@hadoop.apache.org
Message-ID: <245828030.263681263564594807.JavaMail.jira@brutus.apache.org>
Date: Fri, 15 Jan 2010 14:09:54 +0000 (UTC)
From: "Robert Hofstra (JIRA)" <jira@apache.org>
To: hbase-dev@hadoop.apache.org
Subject: [jira] Commented: (HBASE-2104) No exception thrown while during
 scanning no connection can be made to the regionserver
In-Reply-To: <406690237.154551263225174827.JavaMail.jira@brutus.apache.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/HBASE-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12800706#action_12800706 ] 

Robert Hofstra commented on HBASE-2104:
---------------------------------------

In our case, we building a lucune search index with a hadoop from entries in hbase 
When a regionserver is stopped (because it's having problems) this index is smaller, because not all entries are included. 

What I expected, is a failed task in hadoop. Which result in a a new attempt to process the task, which could succeed, when another regionserver is serving the region.

> No exception thrown while during scanning no connection can be made to the regionserver
> ---------------------------------------------------------------------------------------
>
>                 Key: HBASE-2104
>                 URL: https://issues.apache.org/jira/browse/HBASE-2104
>             Project: Hadoop HBase
>          Issue Type: Bug
>          Components: client
>    Affects Versions: 0.20.1
>            Reporter: Robert Hofstra
>
> When a regionservers is stopped (shutdown or crash) and on the same moment a client performs a scan on that regionserver no exception is thrown at client side nor a reconnect toanother regionsserver is tried.
> The ResultScanner.Iterator.hasNext ()just returns false, so the client assumes that there are no records anymore.
> In the ScannerCallable.call I notice that the java.net.ConnectionException is catched and a empyt Result array is returned.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.