You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Mike Drob (JIRA)" <ji...@apache.org> on 2018/04/05 16:53:00 UTC
[jira] [Commented] (HBASE-20354) [DOC] quickstart guide needs to
include note about durability checks for standalone mode
[ https://issues.apache.org/jira/browse/HBASE-20354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16427242#comment-16427242 ]
Mike Drob commented on HBASE-20354:
-----------------------------------
Where do you see this happening? When starting hbase out of a dev workspace, everything works fine for me, and I am pretty sure it uses local disk there.
> [DOC] quickstart guide needs to include note about durability checks for standalone mode
> ----------------------------------------------------------------------------------------
>
> Key: HBASE-20354
> URL: https://issues.apache.org/jira/browse/HBASE-20354
> Project: HBase
> Issue Type: Sub-task
> Components: documentation
> Reporter: Sean Busbey
> Assignee: Sean Busbey
> Priority: Blocker
> Fix For: 2.0.0
>
>
> the current docs for getting started walk through starting a stand alone cluster that relies on the local filesystem, but they don't account for HBASE-19289 so everything falls over.
> Needed configs, probably with more warnings:
> {code}
> <property>
> <name>hbase.procedure.store.wal.use.hsync</name>
> <value>false</value>
> <description>
> Controls whether HBase will call hsync for durability promises on the procedure wal.
> Disable this if you intend to run on LocalFileSystem.
> WARNING: Doing so may expose you to additional risk of data loss!
> </description>
> </property>
> <property>
> <name>hbase.unsafe.stream.capability.enforce</name>
> <value>false</value>
> <description>
> Controls whether HBase will check for stream capabilities (hflush/hsync).
> Disable this if you intend to run on LocalFileSystem.
> WARNING: Doing so may expose you to additional risk of data loss!
> </description>
> </property>
> {code}
> those "may" need to be changed to "will".
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)