hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From st...@apache.org
Subject hbase git commit: HBASE-16973 Revisiting default value for hbase.client.scanner.caching
Date Tue, 01 Nov 2016 16:39:07 GMT
Repository: hbase
Updated Branches:
  refs/heads/master 681b7da19 -> 9cfebf493

HBASE-16973 Revisiting default value for hbase.client.scanner.caching

Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/9cfebf49
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/9cfebf49
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/9cfebf49

Branch: refs/heads/master
Commit: 9cfebf49339f1ce167fbee02b6d6d498eacc0ee5
Parents: 681b7da
Author: Michael Stack <stack@apache.org>
Authored: Tue Nov 1 09:38:51 2016 -0700
Committer: Michael Stack <stack@apache.org>
Committed: Tue Nov 1 09:39:02 2016 -0700

 src/main/asciidoc/_chapters/upgrading.adoc | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/src/main/asciidoc/_chapters/upgrading.adoc b/src/main/asciidoc/_chapters/upgrading.adoc
index 9552024..b0a5565 100644
--- a/src/main/asciidoc/_chapters/upgrading.adoc
+++ b/src/main/asciidoc/_chapters/upgrading.adoc
@@ -226,6 +226,17 @@ NOTE: You cannot do a <<hbase.rolling.upgrade,rolling upgrade>>
from 0.96.x to 1
 There are no known issues running a <<hbase.rolling.upgrade,rolling upgrade>>
from HBase 0.98.x to HBase 1.0.0.
+==== Scanner Caching has Changed
+.From 0.98.x to 1.x
+In hbase-1.x, the default Scan caching 'number of rows' changed.
+Where in 0.98.x, it defaulted to 100, in later HBase versions, the
+default became Integer.MAX_VALUE. Not setting a cache size can make
+for Scans that run for a long time server-side, especially if 
+they are running with stringent filtering.  See
+link:https://issues.apache.org/jira/browse/HBASE-16973[Revisiting default value for hbase.client.scanner.caching];

+for further discussion.
 ==== Upgrading to 1.0 from 0.94
 You cannot rolling upgrade from 0.94.x to 1.x.x.  You must stop your cluster, install the
1.x.x software, run the migration described at <<executing.the.0.96.upgrade>>
(substituting 1.x.x. wherever we make mention of 0.96.x in the section below), and then restart.
Be sure to upgrade your ZooKeeper if it is a version less than the required 3.4.x.

View raw message