[
https://issues.apache.org/jira/browse/HADOOP-2388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12561881#action_12561881
]
Bryan Duxbury commented on HADOOP-2388:
---------------------------------------
Are there any realistic situations in which a scanner is actually unknown, or
are all those situations just LeaseTimedOutExceptions with the wrong name? I
ask because I do not want to mask genuine errors with the wrong message.
> [hbase] When a scanner lease times out, throw a more "user friendly" exception
> ------------------------------------------------------------------------------
>
> Key: HADOOP-2388
> URL: https://issues.apache.org/jira/browse/HADOOP-2388
> Project: Hadoop Core
> Issue Type: Improvement
> Components: contrib/hbase
> Reporter: Jim Kellerman
> Assignee: Bryan Duxbury
> Priority: Trivial
>
> Currently, if a client spends too much time between next() requests on a
> scanner (or between scanner creation and the first call to next), the region
> server will time out the scanner and close. The next call to next() will
> receive an UnknownScannerException because all knowledge of the scanner was
> wiped out on the server when the lease expired.
> The the client side scanner should keep a timer so it compute the elapsed
> time between next() calls so that if it receives an UnknownScannerException,
> it can determine if the scanner lease timed out and if so, throw a more "user
> friendly" exception such as LeaseTimedOutException
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
