diff --git hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md index 9a06b47..47eada3 100644 --- hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md +++ hadoop-yarn-project/hadoop-yarn/hadoop-yarn-site/src/site/markdown/TimelineServiceV2.md @@ -169,6 +169,19 @@ The first part is to set up or pick an Apache HBase cluster to use as the storag version of Apache HBase that is supported with Timeline Service v.2 is 1.1.x. The 1.0.x versions do not work with Timeline Service v.2. The 1.2.x versions have not been tested. +Refer to the HBase book for understanding HBase cluster deployment modes: +http://hbase.apache.org/book.html#standalone_dist + +If you are intent on a simple deploy profile for the Apache HBase cluster +where the data loading is light but the data needs to persist across node +comings and goings, you could consider the "Standalone HBase over HDFS" deploy mode. + +This is a useful variation on standalone hbase and has all hbase daemons running inside one +JVM but rather than persisting to the local filesystem, they persist to an HDFS instance. +Writing to HDFS where data is replicated ensures that data is persisted across node +comings and goings. For more details on this mode, refer to +http://hbase.apache.org/book.html#standalone.over.hdfs + Once you have an Apache HBase cluster ready to use for this purpose, perform the following steps. First, add the timeline service jar to the HBase classpath in all HBase machines in the cluster. It