From 0c81676ea16b63d2c9a7ae1134d485a3437e3c08 Mon Sep 17 00:00:00 2001 From: Misty Stanley-Jones Date: Thu, 23 Oct 2014 14:02:16 +1000 Subject: [PATCH] HBASE-12316 Document scanner timeout troubleshooting for Thrift clients --- src/main/docbkx/troubleshooting.xml | 14 ++++++++++++++ 1 file changed, 14 insertions(+) diff --git a/src/main/docbkx/troubleshooting.xml b/src/main/docbkx/troubleshooting.xml index c2463b0..6ca4d06 100644 --- a/src/main/docbkx/troubleshooting.xml +++ b/src/main/docbkx/troubleshooting.xml @@ -607,6 +607,20 @@ java.lang.Thread.State: WAITING (on object monitor) See . +
+ Performance Differences in Thrift and Java APIs + Poor performance, or even ScannerTimeoutExceptions, can occur if + Scan.setCaching is too high, as discussed in . If the Thrift client uses the wrong caching + settings for a given workload, performance can suffer compared to the Java API. To set + caching for a given scan in the Thrift client, use the scannerGetList(scannerId, + numRows) method, where numRows is an integer representing the number + of rows to cache. In one case, it was found that reducing the cache for Thrift scans from + 1000 to 100 increased performance to near parity with the Java API given the same + queries. + See also Jesse Andersen's blog post + about using Scans with Thrift. +
<classname>LeaseException</classname> when calling -- 2.1.2