[HBASE-24271] Set values in `conf/hbase-site.xml` that enable running on `LocalFileSystem` out of the box - ASF JIRA

XML

Word

Printable

JSON

Details

Type: Task
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 3.0.0-alpha-1, 2.3.0, 1.7.0, 2.2.4
Fix Version/s: 3.0.0-alpha-1, 2.3.0, 1.7.0, 2.2.5
Component/s: None
Labels:
None

Release Note:

Hide

~~HBASE-24271~~ makes changes the the default `conf/hbase-site.xml` such that `bin/hbase` will run directly out of the binary tarball or a compiled source tree without any configuration modifications vs. Hadoop 2.8+. This changes our long-standing history of shipping no configured values in `conf/hbase-site.xml`, so existing processes that assume this file is empty of configuration properties may require attention.

Show
 HBASE-24271 makes changes the the default `conf/hbase-site.xml` such that `bin/hbase` will run directly out of the binary tarball or a compiled source tree without any configuration modifications vs. Hadoop 2.8+. This changes our long-standing history of shipping no configured values in `conf/hbase-site.xml`, so existing processes that assume this file is empty of configuration properties may require attention.

Description

This ticket is to implement the changes as described on the discussion on dev. It reverts and supersedes changes made on ~~HBASE-24086~~ and ~~HBASE-24106~~.

The conclusion I understand from this thread looks something like this:

1. revert ~~HBASE-24086~~, make it so that running on `LocalFileSystem` is a fatal condition with default configs.
2. ship a conf/hbase-site.xml that contains hbase.unsafe.stream.capability.enforce=false, along with a big comment saying this is not safe for production.
3. ship a conf/hbase-site.xml that contains hbase.tmp.dir=./tmp, along with a comment saying herein you'll find temporary and persistent data, reconfigure for production with hbase.rootdir pointed to a durable filesystem that supports our required stream capabilities (see above).
4. update ~~HBASE-24106~~ as appropriate.

Neither 2 nor 3 are suitable for production deployments, thus the changes do not go into hbase-default.xml. Anyone standing up a production deploy must edit hbase-site.xml anyway, so this doesn't change anything. It also restores our "simple" first-time user experience of not needing to run anything besides `bin/start-hbase.sh` (or `bin/hbase master start`, or whatever it is we're telling people these days).

We can reassess this once more when a durable equivalent to LocalFileSystem comes along.