HBASE-12316 Document scanner timeout troubleshooting for Thrift clients

This commit is contained in:
Misty Stanley-Jones 2014-10-23 14:02:16 +10:00
parent f2c83704f4
commit 9ddb25cf3a
1 changed files with 14 additions and 0 deletions

View File

@ -607,6 +607,20 @@ java.lang.Thread.State: WAITING (on object monitor)
<para>See <xref
linkend="perf.hbase.client.caching" />. </para>
</section>
<section>
<title>Performance Differences in Thrift and Java APIs</title>
<para>Poor performance, or even <code>ScannerTimeoutExceptions</code>, can occur if
<code>Scan.setCaching</code> is too high, as discussed in <xref
linkend="trouble.client.scantimeout"/>. 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 <code>scannerGetList(scannerId,
numRows)</code> method, where <code>numRows</code> 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.</para>
<para>See also Jesse Andersen's <link xlink:href="http://blog.cloudera.com/blog/2014/04/how-to-use-the-hbase-thrift-interface-part-3-using-scans/">blog post</link>
about using Scans with Thrift.</para>
</section>
<section
xml:id="trouble.client.lease.exception">
<title><classname>LeaseException</classname> when calling