You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by st...@apache.org on 2016/11/01 16:39:53 UTC
hbase git commit: Revert "HBASE-16973 Revisiting default value for
hbase.client.scanner.caching" Pushed w/ wrong JIRA number
Repository: hbase
Updated Branches:
refs/heads/master 9cfebf493 -> b2d1e21e7
Revert "HBASE-16973 Revisiting default value for hbase.client.scanner.caching"
Pushed w/ wrong JIRA number
This reverts commit 9cfebf49339f1ce167fbee02b6d6d498eacc0ee5.
Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/b2d1e21e
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/b2d1e21e
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/b2d1e21e
Branch: refs/heads/master
Commit: b2d1e21e77644c9b0b5e83dcb662e5b2f71df072
Parents: 9cfebf4
Author: Michael Stack <st...@apache.org>
Authored: Tue Nov 1 09:39:39 2016 -0700
Committer: Michael Stack <st...@apache.org>
Committed: Tue Nov 1 09:39:39 2016 -0700
----------------------------------------------------------------------
src/main/asciidoc/_chapters/upgrading.adoc | 11 -----------
1 file changed, 11 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/hbase/blob/b2d1e21e/src/main/asciidoc/_chapters/upgrading.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/_chapters/upgrading.adoc b/src/main/asciidoc/_chapters/upgrading.adoc
index b0a5565..9552024 100644
--- a/src/main/asciidoc/_chapters/upgrading.adoc
+++ b/src/main/asciidoc/_chapters/upgrading.adoc
@@ -226,17 +226,6 @@ 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.
-[[upgrade1.0.scanner.caching]]
-==== 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.
-
[[upgrade1.0.from.0.94]]
==== 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.