Familiarize yourself with Support and Testing Expectations as well.
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. 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.
instance has all HBase daemons — the Master, Region Servers, and Zoo Keeper — running in a single JVM persisting to the local filesystem. We will show you how to create a table in HBase using the Prior to HBase 0.94.x, HBase expected the loopback IP address to be 127.0.0.1.
By default, unless you configure the This procedure assumes that you have configured Hadoop and HDFS on your local system and/or a remote system, and that they are running and available. The guide on Setting up a Single Node Cluster in the Hadoop documentation is a good starting point.
In reality, you need a fully-distributed configuration to fully test HBase and to use it in real-world scenarios.
This chapter expands upon the Getting Started chapter to further explain configuration of Apache HBase.
Please read this chapter carefully, especially the Basic Prerequisites to ensure that your HBase testing and deployment goes smoothly, and prevent data loss.
For most configurations, a restart is needed for servers to pick up changes.
Dynamic configuration is an exception to this, to be described later below.
In a distributed configuration, the cluster contains multiple nodes, each of which runs one or more HBase daemon.
These include primary and backup Master instances, multiple Zoo Keeper nodes, and multiple Region Server nodes.
This is not the sense in which the term /support/ is used in the context of the Apache HBase project.