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.In the context of Apache HBase, /not tested/ means that a feature or use pattern may or may notwork 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.This guide describes the setup of a standalone HBase instance running against the local filesystem.
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. 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 Ascii Doc from which the finished guide is generated as part of the 'site' build target.
Run 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.
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 [email protected], which allows anyone to send messages, but restricts who can read them.