[
https://issues.apache.org/jira/browse/HBASE-2481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12860548#action_12860548
]
stack commented on HBASE-2481:
------------------------------
I tried the patch and now we seem to do the right thing:
{code}
0000000097
0000000098
0000000099
2010-04-24T09:58:57.642-0700: 62.527: [GC 62.527: [ParNew:
17024K->1870K(19136K), 0.0045580 secs] 21509K->6356K(83008K), 0.0045980 secs]
[Times: user=0.03 sys=0.00, real=0.00 sec
org/apache/hadoop/hbase/client/HTable.java:1991:in `next':
org.apache.hadoop.hbase.client.ScannerTimeoutException: 60007ms passed since
the last invocation, timeout is currently )
from sun.reflect.GeneratedMethodAccessor2:-1:in `invoke'
from sun/reflect/DelegatingMethodAccessorImpl.java:25:in `invoke'
from java/lang/reflect/Method.java:597:in `invoke'
from org/jruby/javasupport/JavaMethod.java:298:in
`invokeWithExceptionHandling'
from org/jruby/javasupport/JavaMethod.java:259:in `invoke'
from org/jruby/java/invokers/InstanceMethodInvoker.java:36:in `call'
from org/jruby/runtime/callsite/CachingCallSite.java:70:in `call'
from bin/slow_scan.rb:27:in `__file__'
from bin/slow_scan.rb:-1:in `load'
from org/jruby/Ruby.java:577:in `runScript'
from org/jruby/Ruby.java:480:in `runNormally'
from org/jruby/Ruby.java:354:in `runFromMain'
from org/jruby/Main.java:229:in `run'
from org/jruby/Main.java:110:in `run'
from org/jruby/Main.java:94:in `main'
Complete Java stackTrace
org.apache.hadoop.hbase.client.ScannerTimeoutException: 60007ms passed since
the last invocation, timeout is currently set to 60000
at
org.apache.hadoop.hbase.client.HTable$ClientScanner.next(HTable.java:1991)
at sun.reflect.GeneratedMethodAccessor2.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.jruby.javasupport.JavaMethod.invokeWithExceptionHandling(JavaMethod.java:298)
at org.jruby.javasupport.JavaMethod.invoke(JavaMethod.java:259)
at
org.jruby.java.invokers.InstanceMethodInvoker.call(InstanceMethodInvoker.java:36)
at
org.jruby.runtime.callsite.CachingCallSite.call(CachingCallSite.java:70)
at bin.slow_scan.__file__(slow_scan.rb:27)
at bin.slow_scan.load(slow_scan.rb)
at org.jruby.Ruby.runScript(Ruby.java:577)
at org.jruby.Ruby.runNormally(Ruby.java:480)
at org.jruby.Ruby.runFromMain(Ruby.java:354)
at org.jruby.Main.run(Main.java:229)
at org.jruby.Main.run(Main.java:110)
at org.jruby.Main.main(Main.java:94)
Caused by: org.apache.hadoop.hbase.UnknownScannerException:
org.apache.hadoop.hbase.UnknownScannerException: Name: 3092528963968774042
at
org.apache.hadoop.hbase.regionserver.HRegionServer.next(HRegionServer.java:1889)
at sun.reflect.GeneratedMethodAccessor12.invoke(Unknown Source)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
...
{code}
> Client is not getting UnknownScannerExceptions; they are being eaten
> --------------------------------------------------------------------
>
> Key: HBASE-2481
> URL: https://issues.apache.org/jira/browse/HBASE-2481
> Project: Hadoop HBase
> Issue Type: Bug
> Affects Versions: 0.20.4
> Reporter: stack
> Priority: Blocker
> Attachments: HBASE-2481.patch
>
>
> This was reported by mudphone on IRC and confirmed by myself in quick test.
> If the client takes too long going back to the RS, the RS will throw an
> UnknownScannerException but it doesn't get back to the client. Instead, the
> client scan silently ends. Marking this blocker. Its actually in 0.20.4.
> Thats what I was testing. Mayhaps an RC sinker?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
