| 失效链接处理 |
|
apache hbase reference guide PDF 下载
本站整理下载：
提取码：5pe7
相关截图：
主要内容：
Preface
This is the official reference guide for the HBase version it ships with.
Herein you will find either the definitive documentation on an HBase topic as of its standing when
the referenced HBase version shipped, or it will point to the location in Javadoc or JIRA where the
pertinent information can be found.
About This Guide
This reference guide is a work in progress. The source for this guide can be found in the
_src/main/asciidoc directory of the HBase source. This reference guide is marked up using AsciiDoc
from which the finished guide is generated as part of the 'site' build target. Run
mvn site
to generate this documentation. Amendments and improvements to the documentation are
welcomed. Click this link to file a new documentation bug against Apache HBase with some values
pre-selected.
Contributing to the Documentation
For an overview of AsciiDoc and suggestions to get started contributing to the documentation, see
the relevant section later in this documentation.
Heads-up if this is your first foray into the world of distributed computing…
If this is your first foray into the wonderful world of Distributed Computing, then you are in for
some interesting times. First off, distributed systems are hard; making a distributed system hum
requires a disparate skillset that spans systems (hardware and software) and networking.
Your cluster’s operation can hiccup because of any of a myriad set of reasons from bugs in HBase
itself through misconfigurations — misconfiguration of HBase but also operating system
misconfigurations — through to hardware problems whether it be a bug in your network card
drivers or an underprovisioned RAM bus (to mention two recent examples of hardware issues that
manifested as "HBase is slow"). You will also need to do a recalibration if up to this your computing
has been bound to a single box. Here is one good starting point: Fallacies of Distributed Computing.
That said, you are welcome.
It’s a fun place to be.
Yours, the HBase Community.
Reporting Bugs
Please use JIRA to report non-security-related bugs.
To protect existing HBase installations from new vulnerabilities, please do not use JIRA to report
security-related bugs. Instead, send your report to the mailing list private@hbase.apache.org, which
allows anyone to send messages, but restricts who can read them. Someone on that list will contact
you to follow up on your report.
Support and Testing Expectations
1
The phrases /supported/, /not supported/, /tested/, and /not tested/ occur several places throughout
this guide. In the interest of clarity, here is a brief explanation of what is generally meant by these
phrases, in the context of HBase.
Commercial technical support for Apache HBase is provided by many Hadoop
vendors. This is not the sense in which the term /support/ is used in the context of
the Apache HBase project. The Apache HBase team assumes no responsibility for
your HBase clusters, your configuration, or your data.
Supported
In the context of Apache HBase, /supported/ means that HBase is designed to work in the way
described, and deviation from the defined behavior or functionality should be reported as a bug.
Not Supported
In the context of Apache HBase, /not supported/ means that a use case or use pattern is not
expected to work and should be considered an antipattern. If you think this designation should
be reconsidered for a given feature or use pattern, file a JIRA or start a discussion on one of the
mailing lists.
Tested
In the context of Apache HBase, /tested/ means that a feature is covered by unit or integration
tests, and has been proven to work as expected.
Not Tested
In the context of Apache HBase, /not tested/ means that a feature or use pattern may or may not
work in a given way, and may or may not corrupt your data or cause operational issues. It is an
unknown, and there are no guarantees. If you can provide proof that a feature designated as
/not tested/ does work in a given way, please submit the tests and/or the metrics so that other
users can gain certainty about such features or use patterns.
2
Getting Started
3
Chapter 1. Introduction
Quickstart will get you up and running on a single-node, standalone instance of HBase.
4
Chapter 2. Quick Start - Standalone HBase
This section describes the setup of a single-node standalone HBase. A standalone instance has all
HBase daemons — the Master, RegionServers, and ZooKeeper — running in a single JVM persisting
to the local filesystem. It is our most basic deploy profile. We will show you how to create a table in
HBase using the hbase shell CLI, insert rows into the table, perform put and scan operations
against the table, enable or disable the table, and start and stop HBase.
Apart from downloading HBase, this procedure should take less than 10 minutes.
2.1. JDK Version Requirements
HBase requires that a JDK be installed. See Java for information about supported JDK versions.
2.2. Get Started with HBase
Procedure: Download, Configure, and Start HBase in Standalone Mode
1. Choose a download site from this list of Apache Download Mirrors. Click on the suggested top
link. This will take you to a mirror of HBase Releases. Click on the folder named stable and then
download the binary file that looks like hbase-<version>-bin.tar.gz.
2. Extract the downloaded file and change to the newly-created directory.
$ tar xzvf hbase-<version>-bin.tar.gz
$ cd hbase-<version>/
3. Set the JAVA_HOME environment variable in conf/hbase-env.sh. First, locate the installation of java
on your machine. On Unix systems, you can use the whereis java command. Once you have the
location, edit conf/hbase-env.sh file, found inside the extracted hbase-<version> directory,
uncomment the line starting with #export JAVA_HOME=, and then set it to your Java installation
path.
Example extract from conf/hbase-env.sh where JAVA_HOME is set
# Set environment variables here.
# The java implementation to use.
export JAVA_HOME=/usr/jdk64/jdk1.8.0_112
4. Optionally set the hbase.tmp.dir property in conf/hbase-site.xml. At this time, you may consider
changing the location on the local filesystem where HBase writes its application data and the
data written by its embedded ZooKeeper instance. By default, HBase uses paths under
hbase.tmp.dir for these directories.
5
On most systems, this is a path created under /tmp. Many system periodically
delete the contents of /tmp. If you start working with HBase in this way, and
then return after the cleanup operation takes place, you’re likely to find
strange errors. The following configuration will place HBase’s runtime data in
a tmp directory found inside the extracted hbase-<version> directory, where it
will be safe from this periodic cleanup.
Open conf/hbase-site.xml and paste the <property> tags between the empty <configuration> tags.
Example 1. Example hbase-site.xml for Standalone HBase
<configuration>
<property>
<name>hbase.tmp.dir</name>
<value>tmp</value>
</property>
</configurati
|
| Java1234官方群25： | 
|
| Java1234官方群25： | 838462530 |
苏公网安备 32061202001004号
