hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jerry...@apache.org
Subject hbase git commit: HBASE-16544 Remove or Clarify 'Using Amazon S3 Storage' section in the reference guide (Yi Liang)
Date Thu, 08 Sep 2016 01:51:07 GMT
Repository: hbase
Updated Branches:
  refs/heads/master e9cfbfd10 -> e65817ef1

HBASE-16544 Remove or Clarify 'Using Amazon S3 Storage' section in the reference guide (Yi

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

Branch: refs/heads/master
Commit: e65817ef15078e262c00d097996852be2716bb87
Parents: e9cfbfd
Author: Jerry He <jerryjch@apache.org>
Authored: Wed Sep 7 18:50:02 2016 -0700
Committer: Jerry He <jerryjch@apache.org>
Committed: Wed Sep 7 18:50:02 2016 -0700

 src/main/asciidoc/_chapters/configuration.adoc | 31 ---------------------
 1 file changed, 31 deletions(-)

diff --git a/src/main/asciidoc/_chapters/configuration.adoc b/src/main/asciidoc/_chapters/configuration.adoc
index 8dc3e8a..89820ca 100644
--- a/src/main/asciidoc/_chapters/configuration.adoc
+++ b/src/main/asciidoc/_chapters/configuration.adoc
@@ -1090,37 +1090,6 @@ Only a subset of all configurations can currently be changed in the
running serv
 Here is an incomplete list: `hbase.regionserver.thread.compaction.large`, `hbase.regionserver.thread.compaction.small`,
`hbase.regionserver.thread.split`, `hbase.regionserver.thread.merge`, as well as compaction
policy and configurations and adjustment to offpeak hours.
 For the full list consult the patch attached to  link:https://issues.apache.org/jira/browse/HBASE-12147[HBASE-12147
Porting Online Config Change from 89-fb].
-== Using Amazon S3 Storage
-HBase is designed to be tightly coupled with HDFS, and testing of other filesystems
-has not been thorough.
-The following limitations have been reported:
-- RegionServers should be deployed in Amazon EC2 to mitigate latency and bandwidth
-limitations when accessing the filesystem, and RegionServers must remain available
-to preserve data locality.
-- S3 writes each inbound and outbound file to disk, which adds overhead to each operation.
-- The best performance is achieved when all clients and servers are in the Amazon
-cloud, rather than a heterogenous architecture.
-- You must be aware of the location of `hadoop.tmp.dir` so that the local `/tmp/`
-directory is not filled to capacity.
-- HBase has a different file usage pattern than MapReduce jobs and has been optimized for
-HDFS, rather than distant networked storage.
-- The `s3a://` protocol is strongly recommended. The `s3n://` and `s3://` protocols have
-limitations and do not use the Amazon AWS SDK. The `s3a://` protocol is supported
-for use with HBase if you use Hadoop 2.6.1 or higher with HBase 1.2 or higher. Hadoop
-2.6.0 is not supported with HBase at all.
-Configuration details for Amazon S3 and associated Amazon services such as EMR are
-out of the scope of the HBase documentation. See the
-link:https://wiki.apache.org/hadoop/AmazonS3[Hadoop Wiki entry on Amazon S3 Storage]
documentation for deploying HBase in EMR].
-One use case that is well-suited for Amazon S3 is storing snapshots. See <<snapshots_s3>>.
 == Index

View raw message