[
https://issues.apache.org/jira/browse/HBASE-17272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15730300#comment-15730300
]
Hudson commented on HBASE-17272:
--------------------------------
FAILURE: Integrated in Jenkins build HBase-Trunk_matrix #2091 (See
[https://builds.apache.org/job/HBase-Trunk_matrix/2091/])
HBASE-17272 Doc how to run Standalone HBase over an HDFS instance; all (stack:
rev 6f25f838c0af80d2deaec91ed13248ce5024bd29)
* (edit) src/main/asciidoc/_chapters/configuration.adoc
* (edit) src/main/asciidoc/_chapters/getting_started.adoc
> Doc how to run Standalone HBase over an HDFS instance; all daemons in one JVM
> but persisting to an HDFS instance
> ----------------------------------------------------------------------------------------------------------------
>
> Key: HBASE-17272
> URL: https://issues.apache.org/jira/browse/HBASE-17272
> Project: HBase
> Issue Type: Task
> Components: documentation
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0
>
> Attachments: 17272.txt, HBASE-17272.master.001.patch,
> HBASE-17272.master.002.patch
>
>
> It is possible to run hbase in standalone mode -- all daemons in the one JVM
> (Master+RegionServers+ZooKeeper) -- but persisting to HDFS rather than the
> usual local filesystem. That this works was news to me. This configuration is
> wanted for the default deploy of the timeline server v2. The standalone mode
> hbase shoudl be good enough for light loading. The persistence to HDFS makes
> it so data can live across the coming and goings of nodes.
> This issue is about doc'ing how to setup this config.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
