Nick Dimiduk created HBASE-24271:
------------------------------------
Summary: Set values in `conf/hbase-site.xml` that enable running
on `LocalFileSystem` out of the box
Key: HBASE-24271
URL: https://issues.apache.org/jira/browse/HBASE-24271
Project: HBase
Issue Type: Task
Affects Versions: 3.0.0, 2.3.0
Reporter: Nick Dimiduk
Assignee: Nick Dimiduk
This ticket is to implement the changes as described on the [discussion on
dev|https://lists.apache.org/thread.html/r089de243a9bc9d923fa07c81e6bc825b82be68f567b892a342a0c61f%40%3Cdev.hbase.apache.org%3E].
It reverts and supersedes changes made on HBASE-24086 and HBASE-24106.
{quote}
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.
{quote}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
