hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mi...@apache.org
Subject [41/52] [partial] hbase-site git commit: Published site at 6d02f36ac78426f178b977566c170fb2e4b3503a.
Date Thu, 16 Jun 2016 22:39:39 GMT
http://git-wip-us.apache.org/repos/asf/hbase-site/blob/b80ecc4e/book.html
----------------------------------------------------------------------
diff --git a/book.html b/book.html
index ffc0029..9cade47 100644
--- a/book.html
+++ b/book.html
@@ -114,164 +114,165 @@
 <li><a href="#security">Securing Apache HBase</a>
 <ul class="sectlevel1">
 <li><a href="#_using_secure_http_https_for_the_web_ui">57. Using Secure HTTP (HTTPS) for the Web UI</a></li>
-<li><a href="#hbase.secure.configuration">58. Secure Client Access to Apache HBase</a></li>
-<li><a href="#hbase.secure.simpleconfiguration">59. Simple User Access to Apache HBase</a></li>
-<li><a href="#_securing_access_to_hdfs_and_zookeeper">60. Securing Access to HDFS and ZooKeeper</a></li>
-<li><a href="#_securing_access_to_your_data">61. Securing Access To Your Data</a></li>
-<li><a href="#security.example.config">62. Security Configuration Example</a></li>
+<li><a href="#hbase.secure.spnego.ui">58. Using SPNEGO for Kerberos authentication with Web UIs</a></li>
+<li><a href="#hbase.secure.configuration">59. Secure Client Access to Apache HBase</a></li>
+<li><a href="#hbase.secure.simpleconfiguration">60. Simple User Access to Apache HBase</a></li>
+<li><a href="#_securing_access_to_hdfs_and_zookeeper">61. Securing Access to HDFS and ZooKeeper</a></li>
+<li><a href="#_securing_access_to_your_data">62. Securing Access To Your Data</a></li>
+<li><a href="#security.example.config">63. Security Configuration Example</a></li>
 </ul>
 </li>
 <li><a href="#_architecture">Architecture</a>
 <ul class="sectlevel1">
-<li><a href="#arch.overview">63. Overview</a></li>
-<li><a href="#arch.catalog">64. Catalog Tables</a></li>
-<li><a href="#architecture.client">65. Client</a></li>
-<li><a href="#client.filter">66. Client Request Filters</a></li>
-<li><a href="#architecture.master">67. Master</a></li>
-<li><a href="#regionserver.arch">68. RegionServer</a></li>
-<li><a href="#regions.arch">69. Regions</a></li>
-<li><a href="#arch.bulk.load">70. Bulk Loading</a></li>
-<li><a href="#arch.hdfs">71. HDFS</a></li>
-<li><a href="#arch.timelineconsistent.reads">72. Timeline-consistent High Available Reads</a></li>
-<li><a href="#hbase_mob">73. Storing Medium-sized Objects (MOB)</a></li>
+<li><a href="#arch.overview">64. Overview</a></li>
+<li><a href="#arch.catalog">65. Catalog Tables</a></li>
+<li><a href="#architecture.client">66. Client</a></li>
+<li><a href="#client.filter">67. Client Request Filters</a></li>
+<li><a href="#architecture.master">68. Master</a></li>
+<li><a href="#regionserver.arch">69. RegionServer</a></li>
+<li><a href="#regions.arch">70. Regions</a></li>
+<li><a href="#arch.bulk.load">71. Bulk Loading</a></li>
+<li><a href="#arch.hdfs">72. HDFS</a></li>
+<li><a href="#arch.timelineconsistent.reads">73. Timeline-consistent High Available Reads</a></li>
+<li><a href="#hbase_mob">74. Storing Medium-sized Objects (MOB)</a></li>
 </ul>
 </li>
 <li><a href="#hbase_apis">Apache HBase APIs</a>
 <ul class="sectlevel1">
-<li><a href="#_examples">74. Examples</a></li>
+<li><a href="#_examples">75. Examples</a></li>
 </ul>
 </li>
 <li><a href="#external_apis">Apache HBase External APIs</a>
 <ul class="sectlevel1">
-<li><a href="#_rest">75. REST</a></li>
-<li><a href="#_thrift">76. Thrift</a></li>
-<li><a href="#c">77. C/C++ Apache HBase Client</a></li>
-<li><a href="#jdo">78. Using Java Data Objects (JDO) with HBase</a></li>
-<li><a href="#scala">79. Scala</a></li>
-<li><a href="#jython">80. Jython</a></li>
+<li><a href="#_rest">76. REST</a></li>
+<li><a href="#_thrift">77. Thrift</a></li>
+<li><a href="#c">78. C/C++ Apache HBase Client</a></li>
+<li><a href="#jdo">79. Using Java Data Objects (JDO) with HBase</a></li>
+<li><a href="#scala">80. Scala</a></li>
+<li><a href="#jython">81. Jython</a></li>
 </ul>
 </li>
 <li><a href="#thrift">Thrift API and Filter Language</a>
 <ul class="sectlevel1">
-<li><a href="#thrift.filter_language">81. Filter Language</a></li>
+<li><a href="#thrift.filter_language">82. Filter Language</a></li>
 </ul>
 </li>
 <li><a href="#spark">HBase and Spark</a>
 <ul class="sectlevel1">
-<li><a href="#_basic_spark">82. Basic Spark</a></li>
-<li><a href="#_spark_streaming">83. Spark Streaming</a></li>
-<li><a href="#_bulk_load">84. Bulk Load</a></li>
-<li><a href="#_sparksql_dataframes">85. SparkSQL/DataFrames</a></li>
+<li><a href="#_basic_spark">83. Basic Spark</a></li>
+<li><a href="#_spark_streaming">84. Spark Streaming</a></li>
+<li><a href="#_bulk_load">85. Bulk Load</a></li>
+<li><a href="#_sparksql_dataframes">86. SparkSQL/DataFrames</a></li>
 </ul>
 </li>
 <li><a href="#cp">Apache HBase Coprocessors</a>
 <ul class="sectlevel1">
-<li><a href="#_coprocessor_overview">86. Coprocessor Overview</a></li>
-<li><a href="#_types_of_coprocessors">87. Types of Coprocessors</a></li>
-<li><a href="#cp_loading">88. Loading Coprocessors</a></li>
-<li><a href="#cp_example">89. Examples</a></li>
-<li><a href="#_guidelines_for_deploying_a_coprocessor">90. Guidelines For Deploying A Coprocessor</a></li>
-<li><a href="#_monitor_time_spent_in_coprocessors">91. Monitor Time Spent in Coprocessors</a></li>
+<li><a href="#_coprocessor_overview">87. Coprocessor Overview</a></li>
+<li><a href="#_types_of_coprocessors">88. Types of Coprocessors</a></li>
+<li><a href="#cp_loading">89. Loading Coprocessors</a></li>
+<li><a href="#cp_example">90. Examples</a></li>
+<li><a href="#_guidelines_for_deploying_a_coprocessor">91. Guidelines For Deploying A Coprocessor</a></li>
+<li><a href="#_monitor_time_spent_in_coprocessors">92. Monitor Time Spent in Coprocessors</a></li>
 </ul>
 </li>
 <li><a href="#performance">Apache HBase Performance Tuning</a>
 <ul class="sectlevel1">
-<li><a href="#perf.os">92. Operating System</a></li>
-<li><a href="#perf.network">93. Network</a></li>
-<li><a href="#jvm">94. Java</a></li>
-<li><a href="#perf.configurations">95. HBase Configurations</a></li>
-<li><a href="#perf.zookeeper">96. ZooKeeper</a></li>
-<li><a href="#perf.schema">97. Schema Design</a></li>
-<li><a href="#perf.general">98. HBase General Patterns</a></li>
-<li><a href="#perf.writing">99. Writing to HBase</a></li>
-<li><a href="#perf.reading">100. Reading from HBase</a></li>
-<li><a href="#perf.deleting">101. Deleting from HBase</a></li>
-<li><a href="#perf.hdfs">102. HDFS</a></li>
-<li><a href="#perf.ec2">103. Amazon EC2</a></li>
-<li><a href="#perf.hbase.mr.cluster">104. Collocating HBase and MapReduce</a></li>
-<li><a href="#perf.casestudy">105. Case Studies</a></li>
+<li><a href="#perf.os">93. Operating System</a></li>
+<li><a href="#perf.network">94. Network</a></li>
+<li><a href="#jvm">95. Java</a></li>
+<li><a href="#perf.configurations">96. HBase Configurations</a></li>
+<li><a href="#perf.zookeeper">97. ZooKeeper</a></li>
+<li><a href="#perf.schema">98. Schema Design</a></li>
+<li><a href="#perf.general">99. HBase General Patterns</a></li>
+<li><a href="#perf.writing">100. Writing to HBase</a></li>
+<li><a href="#perf.reading">101. Reading from HBase</a></li>
+<li><a href="#perf.deleting">102. Deleting from HBase</a></li>
+<li><a href="#perf.hdfs">103. HDFS</a></li>
+<li><a href="#perf.ec2">104. Amazon EC2</a></li>
+<li><a href="#perf.hbase.mr.cluster">105. Collocating HBase and MapReduce</a></li>
+<li><a href="#perf.casestudy">106. Case Studies</a></li>
 </ul>
 </li>
 <li><a href="#trouble">Troubleshooting and Debugging Apache HBase</a>
 <ul class="sectlevel1">
-<li><a href="#trouble.general">106. General Guidelines</a></li>
-<li><a href="#trouble.log">107. Logs</a></li>
-<li><a href="#trouble.resources">108. Resources</a></li>
-<li><a href="#trouble.tools">109. Tools</a></li>
-<li><a href="#trouble.client">110. Client</a></li>
-<li><a href="#trouble.mapreduce">111. MapReduce</a></li>
-<li><a href="#trouble.namenode">112. NameNode</a></li>
-<li><a href="#trouble.network">113. Network</a></li>
-<li><a href="#trouble.rs">114. RegionServer</a></li>
-<li><a href="#trouble.master">115. Master</a></li>
-<li><a href="#trouble.zookeeper">116. ZooKeeper</a></li>
-<li><a href="#trouble.ec2">117. Amazon EC2</a></li>
-<li><a href="#trouble.versions">118. HBase and Hadoop version issues</a></li>
-<li><a href="#_ipc_configuration_conflicts_with_hadoop">119. IPC Configuration Conflicts with Hadoop</a></li>
-<li><a href="#_hbase_and_hdfs">120. HBase and HDFS</a></li>
-<li><a href="#trouble.tests">121. Running unit or integration tests</a></li>
-<li><a href="#trouble.casestudy">122. Case Studies</a></li>
-<li><a href="#trouble.crypto">123. Cryptographic Features</a></li>
-<li><a href="#_operating_system_specific_issues">124. Operating System Specific Issues</a></li>
-<li><a href="#_jdk_issues">125. JDK Issues</a></li>
+<li><a href="#trouble.general">107. General Guidelines</a></li>
+<li><a href="#trouble.log">108. Logs</a></li>
+<li><a href="#trouble.resources">109. Resources</a></li>
+<li><a href="#trouble.tools">110. Tools</a></li>
+<li><a href="#trouble.client">111. Client</a></li>
+<li><a href="#trouble.mapreduce">112. MapReduce</a></li>
+<li><a href="#trouble.namenode">113. NameNode</a></li>
+<li><a href="#trouble.network">114. Network</a></li>
+<li><a href="#trouble.rs">115. RegionServer</a></li>
+<li><a href="#trouble.master">116. Master</a></li>
+<li><a href="#trouble.zookeeper">117. ZooKeeper</a></li>
+<li><a href="#trouble.ec2">118. Amazon EC2</a></li>
+<li><a href="#trouble.versions">119. HBase and Hadoop version issues</a></li>
+<li><a href="#_ipc_configuration_conflicts_with_hadoop">120. IPC Configuration Conflicts with Hadoop</a></li>
+<li><a href="#_hbase_and_hdfs">121. HBase and HDFS</a></li>
+<li><a href="#trouble.tests">122. Running unit or integration tests</a></li>
+<li><a href="#trouble.casestudy">123. Case Studies</a></li>
+<li><a href="#trouble.crypto">124. Cryptographic Features</a></li>
+<li><a href="#_operating_system_specific_issues">125. Operating System Specific Issues</a></li>
+<li><a href="#_jdk_issues">126. JDK Issues</a></li>
 </ul>
 </li>
 <li><a href="#casestudies">Apache HBase Case Studies</a>
 <ul class="sectlevel1">
-<li><a href="#casestudies.overview">126. Overview</a></li>
-<li><a href="#casestudies.schema">127. Schema Design</a></li>
-<li><a href="#casestudies.perftroub">128. Performance/Troubleshooting</a></li>
+<li><a href="#casestudies.overview">127. Overview</a></li>
+<li><a href="#casestudies.schema">128. Schema Design</a></li>
+<li><a href="#casestudies.perftroub">129. Performance/Troubleshooting</a></li>
 </ul>
 </li>
 <li><a href="#ops_mgt">Apache HBase Operational Management</a>
 <ul class="sectlevel1">
-<li><a href="#tools">129. HBase Tools and Utilities</a></li>
-<li><a href="#ops.regionmgt">130. Region Management</a></li>
-<li><a href="#node.management">131. Node Management</a></li>
-<li><a href="#hbase_metrics">132. HBase Metrics</a></li>
-<li><a href="#ops.monitoring">133. HBase Monitoring</a></li>
-<li><a href="#_cluster_replication">134. Cluster Replication</a></li>
-<li><a href="#_running_multiple_workloads_on_a_single_cluster">135. Running Multiple Workloads On a Single Cluster</a></li>
-<li><a href="#ops.backup">136. HBase Backup</a></li>
-<li><a href="#ops.snapshots">137. HBase Snapshots</a></li>
-<li><a href="#snapshots_azure">138. Storing Snapshots in Microsoft Azure Blob Storage</a></li>
-<li><a href="#ops.capacity">139. Capacity Planning and Region Sizing</a></li>
-<li><a href="#table.rename">140. Table Rename</a></li>
+<li><a href="#tools">130. HBase Tools and Utilities</a></li>
+<li><a href="#ops.regionmgt">131. Region Management</a></li>
+<li><a href="#node.management">132. Node Management</a></li>
+<li><a href="#hbase_metrics">133. HBase Metrics</a></li>
+<li><a href="#ops.monitoring">134. HBase Monitoring</a></li>
+<li><a href="#_cluster_replication">135. Cluster Replication</a></li>
+<li><a href="#_running_multiple_workloads_on_a_single_cluster">136. Running Multiple Workloads On a Single Cluster</a></li>
+<li><a href="#ops.backup">137. HBase Backup</a></li>
+<li><a href="#ops.snapshots">138. HBase Snapshots</a></li>
+<li><a href="#snapshots_azure">139. Storing Snapshots in Microsoft Azure Blob Storage</a></li>
+<li><a href="#ops.capacity">140. Capacity Planning and Region Sizing</a></li>
+<li><a href="#table.rename">141. Table Rename</a></li>
 </ul>
 </li>
 <li><a href="#developer">Building and Developing Apache HBase</a>
 <ul class="sectlevel1">
-<li><a href="#getting.involved">141. Getting Involved</a></li>
-<li><a href="#repos">142. Apache HBase Repositories</a></li>
-<li><a href="#_ides">143. IDEs</a></li>
-<li><a href="#build">144. Building Apache HBase</a></li>
-<li><a href="#releasing">145. Releasing Apache HBase</a></li>
-<li><a href="#hbase.rc.voting">146. Voting on Release Candidates</a></li>
-<li><a href="#documentation">147. Generating the HBase Reference Guide</a></li>
-<li><a href="#hbase.org">148. Updating <a href="http://hbase.apache.org">hbase.apache.org</a></a></li>
-<li><a href="#hbase.tests">149. Tests</a></li>
-<li><a href="#developing">150. Developer Guidelines</a></li>
+<li><a href="#getting.involved">142. Getting Involved</a></li>
+<li><a href="#repos">143. Apache HBase Repositories</a></li>
+<li><a href="#_ides">144. IDEs</a></li>
+<li><a href="#build">145. Building Apache HBase</a></li>
+<li><a href="#releasing">146. Releasing Apache HBase</a></li>
+<li><a href="#hbase.rc.voting">147. Voting on Release Candidates</a></li>
+<li><a href="#documentation">148. Generating the HBase Reference Guide</a></li>
+<li><a href="#hbase.org">149. Updating <a href="http://hbase.apache.org">hbase.apache.org</a></a></li>
+<li><a href="#hbase.tests">150. Tests</a></li>
+<li><a href="#developing">151. Developer Guidelines</a></li>
 </ul>
 </li>
 <li><a href="#unit.tests">Unit Testing HBase Applications</a>
 <ul class="sectlevel1">
-<li><a href="#_junit">151. JUnit</a></li>
-<li><a href="#mockito">152. Mockito</a></li>
-<li><a href="#_mrunit">153. MRUnit</a></li>
-<li><a href="#_integration_testing_with_an_hbase_mini_cluster">154. Integration Testing with an HBase Mini-Cluster</a></li>
+<li><a href="#_junit">152. JUnit</a></li>
+<li><a href="#mockito">153. Mockito</a></li>
+<li><a href="#_mrunit">154. MRUnit</a></li>
+<li><a href="#_integration_testing_with_an_hbase_mini_cluster">155. Integration Testing with an HBase Mini-Cluster</a></li>
 </ul>
 </li>
 <li><a href="#zookeeper">ZooKeeper</a>
 <ul class="sectlevel1">
-<li><a href="#_using_existing_zookeeper_ensemble">155. Using existing ZooKeeper ensemble</a></li>
-<li><a href="#zk.sasl.auth">156. SASL Authentication with ZooKeeper</a></li>
+<li><a href="#_using_existing_zookeeper_ensemble">156. Using existing ZooKeeper ensemble</a></li>
+<li><a href="#zk.sasl.auth">157. SASL Authentication with ZooKeeper</a></li>
 </ul>
 </li>
 <li><a href="#community">Community</a>
 <ul class="sectlevel1">
-<li><a href="#_decisions">157. Decisions</a></li>
-<li><a href="#community.roles">158. Community Roles</a></li>
-<li><a href="#hbase.commit.msg.format">159. Commit Message format</a></li>
+<li><a href="#_decisions">158. Decisions</a></li>
+<li><a href="#community.roles">159. Community Roles</a></li>
+<li><a href="#hbase.commit.msg.format">160. Commit Message format</a></li>
 </ul>
 </li>
 <li><a href="#_appendix">Appendix</a>
@@ -281,7 +282,7 @@
 <li><a href="#hbck.in.depth">Appendix C: hbck In Depth</a></li>
 <li><a href="#appendix_acl_matrix">Appendix D: Access Control Matrix</a></li>
 <li><a href="#compression">Appendix E: Compression and Data Block Encoding In HBase</a></li>
-<li><a href="#data.block.encoding.enable">160. Enable Data Block Encoding</a></li>
+<li><a href="#data.block.encoding.enable">161. Enable Data Block Encoding</a></li>
 <li><a href="#sql">Appendix F: SQL over HBase</a></li>
 <li><a href="#ycsb">Appendix G: YCSB</a></li>
 <li><a href="#_hfile_format_2">Appendix H: HFile format</a></li>
@@ -290,8 +291,8 @@
 <li><a href="#asf">Appendix K: HBase and the Apache Software Foundation</a></li>
 <li><a href="#orca">Appendix L: Apache HBase Orca</a></li>
 <li><a href="#tracing">Appendix M: Enabling Dapper-like Tracing in HBase</a></li>
-<li><a href="#tracing.client.modifications">161. Client Modifications</a></li>
-<li><a href="#tracing.client.shell">162. Tracing from HBase Shell</a></li>
+<li><a href="#tracing.client.modifications">162. Client Modifications</a></li>
+<li><a href="#tracing.client.shell">163. Tracing from HBase Shell</a></li>
 <li><a href="#hbase.rpc">Appendix N: 0.95 RPC Specification</a></li>
 </ul>
 </li>
@@ -1417,6 +1418,12 @@ to be described later below.</p>
 </thead>
 <tbody>
 <tr>
+<td class="tableblock halign-left valign-top"><p class="tableblock">1.3</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://search-hadoop.com/m/DHED4Zlz0R1">Not Supported</a></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">yes</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">yes</p></td>
+</tr>
+<tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">1.2</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock"><a href="http://search-hadoop.com/m/DHED4Zlz0R1">Not Supported</a></p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">yes</p></td>
@@ -1593,12 +1600,13 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 </div>
 <table class="tableblock frame-all grid-all spread">
 <colgroup>
-<col style="width: 16%;">
-<col style="width: 16%;">
-<col style="width: 16%;">
-<col style="width: 16%;">
-<col style="width: 16%;">
-<col style="width: 16%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
+<col style="width: 14%;">
 </colgroup>
 <thead>
 <tr>
@@ -1608,6 +1616,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <th class="tableblock halign-left valign-top">HBase-1.0.x (Hadoop 1.x is NOT supported)</th>
 <th class="tableblock halign-left valign-top">HBase-1.1.x</th>
 <th class="tableblock halign-left valign-top">HBase-1.2.x</th>
+<th class="tableblock halign-left valign-top">HBase-1.3.x</th>
 </tr>
 </thead>
 <tbody>
@@ -1618,6 +1627,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-1.1.x</p></td>
@@ -1626,6 +1636,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-0.23.x</p></td>
@@ -1634,6 +1645,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.0.x-alpha</p></td>
@@ -1642,6 +1654,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.1.0-beta</p></td>
@@ -1650,6 +1663,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.2.0</p></td>
@@ -1658,6 +1672,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.3.x</p></td>
@@ -1666,6 +1681,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.4.x</p></td>
@@ -1674,6 +1690,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.5.x</p></td>
@@ -1682,6 +1699,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.6.0</p></td>
@@ -1690,6 +1708,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.6.1+</p></td>
@@ -1698,6 +1717,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.7.0</p></td>
@@ -1706,6 +1726,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">X</p></td>
 </tr>
 <tr>
 <td class="tableblock halign-left valign-top"><p class="tableblock">Hadoop-2.7.1+</p></td>
@@ -1714,6 +1735,7 @@ HBase 0.98 drops support for Hadoop 1.0, deprecates use of Hadoop 1.1+, and HBas
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">NT</p></td>
 <td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">S</p></td>
 </tr>
 </tbody>
 </table>
@@ -10226,7 +10248,64 @@ If you know how to fix this without opening a second port for HTTPS, patches are
 </div>
 </div>
 <div class="sect1">
-<h2 id="hbase.secure.configuration"><a class="anchor" href="#hbase.secure.configuration"></a>58. Secure Client Access to Apache HBase</h2>
+<h2 id="hbase.secure.spnego.ui"><a class="anchor" href="#hbase.secure.spnego.ui"></a>58. Using SPNEGO for Kerberos authentication with Web UIs</h2>
+<div class="sectionbody">
+<div class="paragraph">
+<p>Kerberos-authentication to HBase Web UIs can be enabled via configuring SPNEGO with the <code>hbase.security.authentication.ui</code>
+property in <em>hbase-site.xml</em>. Enabling this authentication requires that HBase is also configured to use Kerberos authentication
+for RPCs (e.g <code>hbase.security.authentication</code> = <code>kerberos</code>).</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="CodeRay highlight"><code data-lang="xml"><span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication.ui<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span>kerberos<span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>Controls what kind of authentication should be used for the HBase web UIs.<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span>
+<span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span>kerberos<span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>The Kerberos keytab file to use for SPNEGO authentication by the web server.<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span></code></pre>
+</div>
+</div>
+<div class="paragraph">
+<p>A number of properties exist to configure SPNEGO authentication for the web server:</p>
+</div>
+<div class="listingblock">
+<div class="content">
+<pre class="CodeRay highlight"><code data-lang="xml"><span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication.spnego.kerberos.principal<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span>HTTP/_HOST@EXAMPLE.COM<span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>Required for SPNEGO, the Kerberos principal to use for SPNEGO authentication by the
+  web server. The _HOST keyword will be automatically substituted with the node's
+  hostname.<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span>
+<span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication.spnego.kerberos.keytab<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span>/etc/security/keytabs/spnego.service.keytab<span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>Required for SPNEGO, the Kerberos keytab file to use for SPNEGO authentication by the
+  web server.<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span>
+<span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication.spnego.kerberos.name.rules<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span><span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>Optional, Hadoop-style `auth_to_local` rules which will be parsed and used in the
+  handling of Kerberos principals<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span>
+<span class="tag">&lt;property&gt;</span>
+  <span class="tag">&lt;name&gt;</span>hbase.security.authentication.signature.secret.file<span class="tag">&lt;/name&gt;</span>
+  <span class="tag">&lt;value&gt;</span><span class="tag">&lt;/value&gt;</span>
+  <span class="tag">&lt;description&gt;</span>Optional, a file whose contents will be used as a secret to sign the HTTP cookies
+  as a part of the SPNEGO authentication handshake. If this is not provided, Java's `Random` library
+  will be used for the secret.<span class="tag">&lt;/description&gt;</span>
+<span class="tag">&lt;/property&gt;</span></code></pre>
+</div>
+</div>
+</div>
+</div>
+<div class="sect1">
+<h2 id="hbase.secure.configuration"><a class="anchor" href="#hbase.secure.configuration"></a>59. Secure Client Access to Apache HBase</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Newer releases of Apache HBase (&gt;= 0.92) support optional SASL authentication of clients.
@@ -10236,7 +10315,7 @@ See also Matteo Bertozzi&#8217;s article on <a href="http://www.cloudera.com/blo
 <p>This describes how to set up Apache HBase and clients for connection to secure HBase resources.</p>
 </div>
 <div class="sect2">
-<h3 id="security.prerequisites"><a class="anchor" href="#security.prerequisites"></a>58.1. Prerequisites</h3>
+<h3 id="security.prerequisites"><a class="anchor" href="#security.prerequisites"></a>59.1. Prerequisites</h3>
 <div class="dlist">
 <dl>
 <dt class="hdlist1">Hadoop Authentication Configuration</dt>
@@ -10253,7 +10332,7 @@ Otherwise, you would be using strong authentication for HBase but not for the un
 </div>
 </div>
 <div class="sect2">
-<h3 id="_server_side_configuration_for_secure_operation"><a class="anchor" href="#_server_side_configuration_for_secure_operation"></a>58.2. Server-side Configuration for Secure Operation</h3>
+<h3 id="_server_side_configuration_for_secure_operation"><a class="anchor" href="#_server_side_configuration_for_secure_operation"></a>59.2. Server-side Configuration for Secure Operation</h3>
 <div class="paragraph">
 <p>First, refer to <a href="#security.prerequisites">security.prerequisites</a> and ensure that your underlying HDFS configuration is secure.</p>
 </div>
@@ -10281,7 +10360,7 @@ Otherwise, you would be using strong authentication for HBase but not for the un
 </div>
 </div>
 <div class="sect2">
-<h3 id="_client_side_configuration_for_secure_operation"><a class="anchor" href="#_client_side_configuration_for_secure_operation"></a>58.3. Client-side Configuration for Secure Operation</h3>
+<h3 id="_client_side_configuration_for_secure_operation"><a class="anchor" href="#_client_side_configuration_for_secure_operation"></a>59.3. Client-side Configuration for Secure Operation</h3>
 <div class="paragraph">
 <p>First, refer to <a href="#security.prerequisites">Prerequisites</a> and ensure that your underlying HDFS configuration is secure.</p>
 </div>
@@ -10335,7 +10414,7 @@ conf.set(<span class="string"><span class="delimiter">&quot;</span><span class="
 </div>
 </div>
 <div class="sect2">
-<h3 id="security.client.thrift"><a class="anchor" href="#security.client.thrift"></a>58.4. Client-side Configuration for Secure Operation - Thrift Gateway</h3>
+<h3 id="security.client.thrift"><a class="anchor" href="#security.client.thrift"></a>59.4. Client-side Configuration for Secure Operation - Thrift Gateway</h3>
 <div class="paragraph">
 <p>Add the following to the <code>hbase-site.xml</code> file for every Thrift gateway:</p>
 </div>
@@ -10385,7 +10464,7 @@ All client access via the Thrift gateway will use the Thrift gateway&#8217;s cre
 </div>
 </div>
 <div class="sect2">
-<h3 id="security.gateway.thrift"><a class="anchor" href="#security.gateway.thrift"></a>58.5. Configure the Thrift Gateway to Authenticate on Behalf of the Client</h3>
+<h3 id="security.gateway.thrift"><a class="anchor" href="#security.gateway.thrift"></a>59.5. Configure the Thrift Gateway to Authenticate on Behalf of the Client</h3>
 <div class="paragraph">
 <p><a href="#security.client.thrift">Client-side Configuration for Secure Operation - Thrift Gateway</a> describes how to authenticate a Thrift client to HBase using a fixed user.
 As an alternative, you can configure the Thrift gateway to authenticate to HBase on the client&#8217;s behalf, and to access HBase using a proxy user.
@@ -10443,7 +10522,7 @@ To start Thrift on a node, run the command <code>bin/hbase-daemon.sh start thrif
 </div>
 </div>
 <div class="sect2">
-<h3 id="security.gateway.thrift.doas"><a class="anchor" href="#security.gateway.thrift.doas"></a>58.6. Configure the Thrift Gateway to Use the <code>doAs</code> Feature</h3>
+<h3 id="security.gateway.thrift.doas"><a class="anchor" href="#security.gateway.thrift.doas"></a>59.6. Configure the Thrift Gateway to Use the <code>doAs</code> Feature</h3>
 <div class="paragraph">
 <p><a href="#security.gateway.thrift">Configure the Thrift Gateway to Authenticate on Behalf of the Client</a> describes how to configure the Thrift gateway to authenticate to HBase on the client&#8217;s behalf, and to access HBase using a proxy user. The limitation of this approach is that after the client is initialized with a particular set of credentials, it cannot change these credentials during the session. The <code>doAs</code> feature provides a flexible way to impersonate multiple principals using the same client. This feature was implemented in <a href="https://issues.apache.org/jira/browse/HBASE-12640">HBASE-12640</a> for Thrift 1, but is currently not available for Thrift 2.</p>
 </div>
@@ -10488,7 +10567,7 @@ to get an overall idea of how to use this feature in your client.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_client_side_configuration_for_secure_operation_rest_gateway"><a class="anchor" href="#_client_side_configuration_for_secure_operation_rest_gateway"></a>58.7. Client-side Configuration for Secure Operation - REST Gateway</h3>
+<h3 id="_client_side_configuration_for_secure_operation_rest_gateway"><a class="anchor" href="#_client_side_configuration_for_secure_operation_rest_gateway"></a>59.7. Client-side Configuration for Secure Operation - REST Gateway</h3>
 <div class="paragraph">
 <p>Add the following to the <code>hbase-site.xml</code> file for every REST gateway:</p>
 </div>
@@ -10565,7 +10644,7 @@ For more information, refer to <a href="http://hadoop.apache.org/docs/stable/had
 </div>
 </div>
 <div class="sect2">
-<h3 id="security.rest.gateway"><a class="anchor" href="#security.rest.gateway"></a>58.8. REST Gateway Impersonation Configuration</h3>
+<h3 id="security.rest.gateway"><a class="anchor" href="#security.rest.gateway"></a>59.8. REST Gateway Impersonation Configuration</h3>
 <div class="paragraph">
 <p>By default, the REST gateway doesn&#8217;t support impersonation.
 It accesses the HBase on behalf of clients as the user configured as in the previous section.
@@ -10627,7 +10706,7 @@ So it can apply proper authorizations.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="hbase.secure.simpleconfiguration"><a class="anchor" href="#hbase.secure.simpleconfiguration"></a>59. Simple User Access to Apache HBase</h2>
+<h2 id="hbase.secure.simpleconfiguration"><a class="anchor" href="#hbase.secure.simpleconfiguration"></a>60. Simple User Access to Apache HBase</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Newer releases of Apache HBase (&gt;= 0.92) support optional SASL authentication of clients.
@@ -10637,7 +10716,7 @@ See also Matteo Bertozzi&#8217;s article on <a href="http://www.cloudera.com/blo
 <p>This describes how to set up Apache HBase and clients for simple user access to HBase resources.</p>
 </div>
 <div class="sect2">
-<h3 id="_simple_versus_secure_access"><a class="anchor" href="#_simple_versus_secure_access"></a>59.1. Simple versus Secure Access</h3>
+<h3 id="_simple_versus_secure_access"><a class="anchor" href="#_simple_versus_secure_access"></a>60.1. Simple versus Secure Access</h3>
 <div class="paragraph">
 <p>The following section shows how to set up simple user access.
 Simple user access is not a secure method of operating HBase.
@@ -10651,13 +10730,13 @@ Refer to the section <a href="#hbase.secure.configuration">Secure Client Access
 </div>
 </div>
 <div class="sect2">
-<h3 id="_prerequisites"><a class="anchor" href="#_prerequisites"></a>59.2. Prerequisites</h3>
+<h3 id="_prerequisites"><a class="anchor" href="#_prerequisites"></a>60.2. Prerequisites</h3>
 <div class="paragraph">
 <p>None</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_server_side_configuration_for_simple_user_access_operation"><a class="anchor" href="#_server_side_configuration_for_simple_user_access_operation"></a>59.3. Server-side Configuration for Simple User Access Operation</h3>
+<h3 id="_server_side_configuration_for_simple_user_access_operation"><a class="anchor" href="#_server_side_configuration_for_simple_user_access_operation"></a>60.3. Server-side Configuration for Simple User Access Operation</h3>
 <div class="paragraph">
 <p>Add the following to the <code>hbase-site.xml</code> file on every server machine in the cluster:</p>
 </div>
@@ -10709,7 +10788,7 @@ Refer to the section <a href="#hbase.secure.configuration">Secure Client Access
 </div>
 </div>
 <div class="sect2">
-<h3 id="_client_side_configuration_for_simple_user_access_operation"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation"></a>59.4. Client-side Configuration for Simple User Access Operation</h3>
+<h3 id="_client_side_configuration_for_simple_user_access_operation"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation"></a>60.4. Client-side Configuration for Simple User Access Operation</h3>
 <div class="paragraph">
 <p>Add the following to the <code>hbase-site.xml</code> file on every client:</p>
 </div>
@@ -10736,7 +10815,7 @@ Refer to the section <a href="#hbase.secure.configuration">Secure Client Access
 <p>Be advised that if the <code>hbase.security.authentication</code> in the client- and server-side site files do not match, the client will not be able to communicate with the cluster.</p>
 </div>
 <div class="sect3">
-<h4 id="_client_side_configuration_for_simple_user_access_operation_thrift_gateway"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation_thrift_gateway"></a>59.4.1. Client-side Configuration for Simple User Access Operation - Thrift Gateway</h4>
+<h4 id="_client_side_configuration_for_simple_user_access_operation_thrift_gateway"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation_thrift_gateway"></a>60.4.1. Client-side Configuration for Simple User Access Operation - Thrift Gateway</h4>
 <div class="paragraph">
 <p>The Thrift gateway user will need access.
 For example, to give the Thrift API user, <code>thrift_server</code>, administrative access, a command such as this one will suffice:</p>
@@ -10756,7 +10835,7 @@ All client access via the Thrift gateway will use the Thrift gateway&#8217;s cre
 </div>
 </div>
 <div class="sect3">
-<h4 id="_client_side_configuration_for_simple_user_access_operation_rest_gateway"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation_rest_gateway"></a>59.4.2. Client-side Configuration for Simple User Access Operation - REST Gateway</h4>
+<h4 id="_client_side_configuration_for_simple_user_access_operation_rest_gateway"><a class="anchor" href="#_client_side_configuration_for_simple_user_access_operation_rest_gateway"></a>60.4.2. Client-side Configuration for Simple User Access Operation - REST Gateway</h4>
 <div class="paragraph">
 <p>The REST gateway will authenticate with HBase using the supplied credential.
 No authentication will be performed by the REST gateway itself.
@@ -10783,13 +10862,13 @@ This is future work.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_securing_access_to_hdfs_and_zookeeper"><a class="anchor" href="#_securing_access_to_hdfs_and_zookeeper"></a>60. Securing Access to HDFS and ZooKeeper</h2>
+<h2 id="_securing_access_to_hdfs_and_zookeeper"><a class="anchor" href="#_securing_access_to_hdfs_and_zookeeper"></a>61. Securing Access to HDFS and ZooKeeper</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Secure HBase requires secure ZooKeeper and HDFS so that users cannot access and/or modify the metadata and data from under HBase. HBase uses HDFS (or configured file system) to keep its data files as well as write ahead logs (WALs) and other data. HBase uses ZooKeeper to store some metadata for operations (master address, table locks, recovery state, etc).</p>
 </div>
 <div class="sect2">
-<h3 id="_securing_zookeeper_data"><a class="anchor" href="#_securing_zookeeper_data"></a>60.1. Securing ZooKeeper Data</h3>
+<h3 id="_securing_zookeeper_data"><a class="anchor" href="#_securing_zookeeper_data"></a>61.1. Securing ZooKeeper Data</h3>
 <div class="paragraph">
 <p>ZooKeeper has a pluggable authentication mechanism to enable access from clients using different methods. ZooKeeper even allows authenticated and un-authenticated clients at the same time. The access to znodes can be restricted by providing Access Control Lists (ACLs) per znode. An ACL contains two components, the authentication method and the principal. ACLs are NOT enforced hierarchically. See <a href="https://zookeeper.apache.org/doc/r3.3.6/zookeeperProgrammers.html#sc_ZooKeeperPluggableAuthentication">ZooKeeper Programmers Guide</a> for details.</p>
 </div>
@@ -10798,7 +10877,7 @@ This is future work.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_securing_file_system_hdfs_data"><a class="anchor" href="#_securing_file_system_hdfs_data"></a>60.2. Securing File System (HDFS) Data</h3>
+<h3 id="_securing_file_system_hdfs_data"><a class="anchor" href="#_securing_file_system_hdfs_data"></a>61.2. Securing File System (HDFS) Data</h3>
 <div class="paragraph">
 <p>All of the data under management is kept under the root directory in the file system (<code>hbase.rootdir</code>). Access to the data and WAL files in the filesystem should be restricted so that users cannot bypass the HBase layer, and peek at the underlying data files from the file system. HBase assumes the filesystem used (HDFS or other) enforces permissions hierarchically. If sufficient protection from the file system (both authorization and authentication) is not provided, HBase level authorization control (ACLs, visibility labels, etc) is meaningless since the user can always access the data from the file system.</p>
 </div>
@@ -10820,7 +10899,7 @@ This is future work.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="_securing_access_to_your_data"><a class="anchor" href="#_securing_access_to_your_data"></a>61. Securing Access To Your Data</h2>
+<h2 id="_securing_access_to_your_data"><a class="anchor" href="#_securing_access_to_your_data"></a>62. Securing Access To Your Data</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>After you have configured secure authentication between HBase client and server processes and gateways, you need to consider the security of your data itself.
@@ -10899,7 +10978,7 @@ This is the default for HBase 1.0 and newer.</p>
 </ol>
 </div>
 <div class="sect2">
-<h3 id="hbase.tags"><a class="anchor" href="#hbase.tags"></a>61.1. Tags</h3>
+<h3 id="hbase.tags"><a class="anchor" href="#hbase.tags"></a>62.1. Tags</h3>
 <div class="paragraph">
 <p><em class="firstterm">Tags</em> are a feature of HFile v3.
 A tag is a piece of metadata which is part of a cell, separate from the key, value, and version.
@@ -10909,7 +10988,7 @@ It is possible that in the future, tags will be used to implement other HBase fe
 You don&#8217;t need to know a lot about tags in order to use the security features they enable.</p>
 </div>
 <div class="sect3">
-<h4 id="_implementation_details"><a class="anchor" href="#_implementation_details"></a>61.1.1. Implementation Details</h4>
+<h4 id="_implementation_details"><a class="anchor" href="#_implementation_details"></a>62.1.1. Implementation Details</h4>
 <div class="paragraph">
 <p>Every cell can have zero or more tags.
 Every tag has a type and the actual tag byte array.</p>
@@ -10930,9 +11009,9 @@ Tag compression uses dictionary encoding.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="hbase.accesscontrol.configuration"><a class="anchor" href="#hbase.accesscontrol.configuration"></a>61.2. Access Control Labels (ACLs)</h3>
+<h3 id="hbase.accesscontrol.configuration"><a class="anchor" href="#hbase.accesscontrol.configuration"></a>62.2. Access Control Labels (ACLs)</h3>
 <div class="sect3">
-<h4 id="_how_it_works"><a class="anchor" href="#_how_it_works"></a>61.2.1. How It Works</h4>
+<h4 id="_how_it_works"><a class="anchor" href="#_how_it_works"></a>62.2.1. How It Works</h4>
 <div class="paragraph">
 <p>ACLs in HBase are based upon a user&#8217;s membership in or exclusion from groups, and a given group&#8217;s permissions to access a given resource.
 ACLs are implemented as a coprocessor called AccessController.</p>
@@ -11597,7 +11676,7 @@ hbase&gt; user_permission JAVA_REGEX</pre>
 </div>
 </div>
 <div class="sect2">
-<h3 id="hbase.visibility.labels"><a class="anchor" href="#hbase.visibility.labels"></a>61.3. Visibility Labels</h3>
+<h3 id="hbase.visibility.labels"><a class="anchor" href="#hbase.visibility.labels"></a>62.3. Visibility Labels</h3>
 <div class="paragraph">
 <p>Visibility labels control can be used to only permit users or principals associated with a given label to read or access cells with that label.
 For instance, you might label a cell <code>top-secret</code>, and only grant access to that label to the <code>managers</code> group.
@@ -11710,7 +11789,7 @@ Visibility labels are not currently applied for superusers.
 </tbody>
 </table>
 <div class="sect3">
-<h4 id="_server_side_configuration_2"><a class="anchor" href="#_server_side_configuration_2"></a>61.3.1. Server-Side Configuration</h4>
+<h4 id="_server_side_configuration_2"><a class="anchor" href="#_server_side_configuration_2"></a>62.3.1. Server-Side Configuration</h4>
 <div class="olist arabic">
 <ol class="arabic">
 <li>
@@ -11760,7 +11839,7 @@ In that case, the mutation will fail if it makes use of labels the user is not a
 </div>
 </div>
 <div class="sect3">
-<h4 id="_administration_2"><a class="anchor" href="#_administration_2"></a>61.3.2. Administration</h4>
+<h4 id="_administration_2"><a class="anchor" href="#_administration_2"></a>62.3.2. Administration</h4>
 <div class="paragraph">
 <p>Administration tasks can be performed using the HBase Shell or the Java API.
 For defining the list of visibility labels and associating labels with users, the HBase Shell is probably simpler.</p>
@@ -11994,7 +12073,7 @@ The correct way to apply cell level labels is to do so in the application code w
 </div>
 </div>
 <div class="sect3">
-<h4 id="reading_cells_with_labels"><a class="anchor" href="#reading_cells_with_labels"></a>61.3.3. Reading Cells with Labels</h4>
+<h4 id="reading_cells_with_labels"><a class="anchor" href="#reading_cells_with_labels"></a>62.3.3. Reading Cells with Labels</h4>
 <div class="paragraph">
 <p>When you issue a Scan or Get, HBase uses your default set of authorizations to
 filter out cells that you do not have access to. A superuser can set the default
@@ -12055,7 +12134,7 @@ public <span class="predefined-type">Void</span> run() <span class="directive">t
 </div>
 </div>
 <div class="sect3">
-<h4 id="_implementing_your_own_visibility_label_algorithm"><a class="anchor" href="#_implementing_your_own_visibility_label_algorithm"></a>61.3.4. Implementing Your Own Visibility Label Algorithm</h4>
+<h4 id="_implementing_your_own_visibility_label_algorithm"><a class="anchor" href="#_implementing_your_own_visibility_label_algorithm"></a>62.3.4. Implementing Your Own Visibility Label Algorithm</h4>
 <div class="paragraph">
 <p>Interpreting the labels authenticated for a given get/scan request is a pluggable algorithm.</p>
 </div>
@@ -12067,7 +12146,7 @@ public <span class="predefined-type">Void</span> run() <span class="directive">t
 </div>
 </div>
 <div class="sect3">
-<h4 id="_replicating_visibility_tags_as_strings"><a class="anchor" href="#_replicating_visibility_tags_as_strings"></a>61.3.5. Replicating Visibility Tags as Strings</h4>
+<h4 id="_replicating_visibility_tags_as_strings"><a class="anchor" href="#_replicating_visibility_tags_as_strings"></a>62.3.5. Replicating Visibility Tags as Strings</h4>
 <div class="paragraph">
 <p>As mentioned in the above sections, the interface <code>VisibilityLabelService</code> could be used to implement a different way of storing the visibility expressions in the cells. Clusters with replication enabled also must replicate the visibility expressions to the peer cluster. If <code>DefaultVisibilityLabelServiceImpl</code> is used as the implementation for <code>VisibilityLabelService</code>, all the visibility expression are converted to the corresponding expression based on the ordinals for each visibility label stored in the labels table. During replication, visible cells are also replicated with the ordinal-based expression intact. The peer cluster may not have the same <code>labels</code> table with the same ordinal mapping for the visibility labels. In that case, replicating the ordinals makes no sense. It would be better if the replication occurred with the visibility expressions transmitted as strings. To replicate the visibility expression as strings to the peer 
 cluster, create a <code>RegionServerObserver</code> configuration which works based on the implementation of the <code>VisibilityLabelService</code> interface. The configuration below enables replication of visibility expressions to peer clusters as strings. See <a href="https://issues.apache.org/jira/browse/HBASE-11639">HBASE-11639</a> for more details.</p>
 </div>
@@ -12082,7 +12161,7 @@ public <span class="predefined-type">Void</span> run() <span class="directive">t
 </div>
 </div>
 <div class="sect2">
-<h3 id="hbase.encryption.server"><a class="anchor" href="#hbase.encryption.server"></a>61.4. Transparent Encryption of Data At Rest</h3>
+<h3 id="hbase.encryption.server"><a class="anchor" href="#hbase.encryption.server"></a>62.4. Transparent Encryption of Data At Rest</h3>
 <div class="paragraph">
 <p>HBase provides a mechanism for protecting your data at rest, in HFiles and the WAL, which reside within HDFS or another distributed filesystem.
 A two-tier architecture is used for flexible and non-intrusive key rotation.
@@ -12091,7 +12170,7 @@ When data is written, it is encrypted.
 When it is read, it is decrypted on demand.</p>
 </div>
 <div class="sect3">
-<h4 id="_how_it_works_2"><a class="anchor" href="#_how_it_works_2"></a>61.4.1. How It Works</h4>
+<h4 id="_how_it_works_2"><a class="anchor" href="#_how_it_works_2"></a>62.4.1. How It Works</h4>
 <div class="paragraph">
 <p>The administrator provisions a master key for the cluster, which is stored in a key provider accessible to every trusted HBase process, including the HMaster, RegionServers, and clients (such as HBase Shell) on administrative workstations.
 The default key provider is integrated with the Java KeyStore API and any key management systems with support for it.
@@ -12122,7 +12201,7 @@ When WAL encryption is enabled, all WALs are encrypted, regardless of whether th
 </div>
 </div>
 <div class="sect3">
-<h4 id="_server_side_configuration_3"><a class="anchor" href="#_server_side_configuration_3"></a>61.4.2. Server-Side Configuration</h4>
+<h4 id="_server_side_configuration_3"><a class="anchor" href="#_server_side_configuration_3"></a>62.4.2. Server-Side Configuration</h4>
 <div class="paragraph">
 <p>This procedure assumes you are using the default Java keystore implementation.
 If you are using a custom implementation, check its documentation and adjust accordingly.</p>
@@ -12277,7 +12356,7 @@ You can include these in the HMaster&#8217;s <em>hbase-site.xml</em> as well, bu
 </div>
 </div>
 <div class="sect3">
-<h4 id="_administration_3"><a class="anchor" href="#_administration_3"></a>61.4.3. Administration</h4>
+<h4 id="_administration_3"><a class="anchor" href="#_administration_3"></a>62.4.3. Administration</h4>
 <div class="paragraph">
 <p>Administrative tasks can be performed in HBase Shell or the Java API.</p>
 </div>
@@ -12331,7 +12410,7 @@ Next, configure fallback to the old master key in the <em>hbase-site.xml</em> fi
 </div>
 </div>
 <div class="sect2">
-<h3 id="hbase.secure.bulkload"><a class="anchor" href="#hbase.secure.bulkload"></a>61.5. Secure Bulk Load</h3>
+<h3 id="hbase.secure.bulkload"><a class="anchor" href="#hbase.secure.bulkload"></a>62.5. Secure Bulk Load</h3>
 <div class="paragraph">
 <p>Bulk loading in secure mode is a bit more involved than normal setup, since the client has to transfer the ownership of the files generated from the MapReduce job to HBase.
 Secure bulk loading is implemented by a coprocessor, named
@@ -12388,7 +12467,7 @@ HBase manages creation and deletion of this directory.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="security.example.config"><a class="anchor" href="#security.example.config"></a>62. Security Configuration Example</h2>
+<h2 id="security.example.config"><a class="anchor" href="#security.example.config"></a>63. Security Configuration Example</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>This configuration example includes support for HFile v3, ACLs, Visibility Labels, and transparent encryption of data at rest and the WAL.
@@ -12538,10 +12617,10 @@ All options have been discussed separately in the sections above.</p>
 </div>
 <h1 id="_architecture" class="sect0"><a class="anchor" href="#_architecture"></a>Architecture</h1>
 <div class="sect1">
-<h2 id="arch.overview"><a class="anchor" href="#arch.overview"></a>63. Overview</h2>
+<h2 id="arch.overview"><a class="anchor" href="#arch.overview"></a>64. Overview</h2>
 <div class="sectionbody">
 <div class="sect2">
-<h3 id="arch.overview.nosql"><a class="anchor" href="#arch.overview.nosql"></a>63.1. NoSQL?</h3>
+<h3 id="arch.overview.nosql"><a class="anchor" href="#arch.overview.nosql"></a>64.1. NoSQL?</h3>
 <div class="paragraph">
 <p>HBase is a type of "NoSQL" database.
 "NoSQL" is a general term meaning that the database isn&#8217;t an RDBMS which supports SQL as its primary access language, but there are many types of NoSQL databases: BerkeleyDB is an example of a local NoSQL database, whereas HBase is very much a distributed database.
@@ -12589,7 +12668,7 @@ This makes it very suitable for tasks such as high-speed counter aggregation.</p
 </div>
 </div>
 <div class="sect2">
-<h3 id="arch.overview.when"><a class="anchor" href="#arch.overview.when"></a>63.2. When Should I Use HBase?</h3>
+<h3 id="arch.overview.when"><a class="anchor" href="#arch.overview.when"></a>64.2. When Should I Use HBase?</h3>
 <div class="paragraph">
 <p>HBase isn&#8217;t suitable for every problem.</p>
 </div>
@@ -12611,7 +12690,7 @@ Even HDFS doesn&#8217;t do well with anything less than 5 DataNodes (due to thin
 </div>
 </div>
 <div class="sect2">
-<h3 id="arch.overview.hbasehdfs"><a class="anchor" href="#arch.overview.hbasehdfs"></a>63.3. What Is The Difference Between HBase and Hadoop/HDFS?</h3>
+<h3 id="arch.overview.hbasehdfs"><a class="anchor" href="#arch.overview.hbasehdfs"></a>64.3. What Is The Difference Between HBase and Hadoop/HDFS?</h3>
 <div class="paragraph">
 <p><a href="http://hadoop.apache.org/hdfs/">HDFS</a> is a distributed file system that is well suited for the storage of large files.
 Its documentation states that it is not, however, a general purpose file system, and does not provide fast individual record lookups in files.
@@ -12624,13 +12703,13 @@ See the <a href="#datamodel">Data Model</a> and the rest of this chapter for mor
 </div>
 </div>
 <div class="sect1">
-<h2 id="arch.catalog"><a class="anchor" href="#arch.catalog"></a>64. Catalog Tables</h2>
+<h2 id="arch.catalog"><a class="anchor" href="#arch.catalog"></a>65. Catalog Tables</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The catalog table <code>hbase:meta</code> exists as an HBase table and is filtered out of the HBase shell&#8217;s <code>list</code> command, but is in fact a table just like any other.</p>
 </div>
 <div class="sect2">
-<h3 id="arch.catalog.root"><a class="anchor" href="#arch.catalog.root"></a>64.1. -ROOT-</h3>
+<h3 id="arch.catalog.root"><a class="anchor" href="#arch.catalog.root"></a>65.1. -ROOT-</h3>
 <div class="admonitionblock note">
 <table>
 <tr>
@@ -12673,7 +12752,7 @@ region key (<code>.META.,,1</code>)</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="arch.catalog.meta"><a class="anchor" href="#arch.catalog.meta"></a>64.2. hbase:meta</h3>
+<h3 id="arch.catalog.meta"><a class="anchor" href="#arch.catalog.meta"></a>65.2. hbase:meta</h3>
 <div class="paragraph">
 <p>The <code>hbase:meta</code> table (previously called <code>.META.</code>) keeps a list of all regions in the system.
 The location of <code>hbase:meta</code> was previously tracked within the <code>-ROOT-</code> table, but is now stored in ZooKeeper.</p>
@@ -12734,7 +12813,7 @@ utility.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="arch.catalog.startup"><a class="anchor" href="#arch.catalog.startup"></a>64.3. Startup Sequencing</h3>
+<h3 id="arch.catalog.startup"><a class="anchor" href="#arch.catalog.startup"></a>65.3. Startup Sequencing</h3>
 <div class="paragraph">
 <p>First, the location of <code>hbase:meta</code> is looked up in ZooKeeper.
 Next, <code>hbase:meta</code> is updated with server and startcode values.</p>
@@ -12746,7 +12825,7 @@ Next, <code>hbase:meta</code> is updated with server and startcode values.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="architecture.client"><a class="anchor" href="#architecture.client"></a>65. Client</h2>
+<h2 id="architecture.client"><a class="anchor" href="#architecture.client"></a>66. Client</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>The HBase client finds the RegionServers that are serving the particular row range of interest.
@@ -12763,12 +12842,12 @@ Should a region be reassigned either by the master load balancer or because a Re
 <p>Administrative functions are done via an instance of <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Admin.html">Admin</a></p>
 </div>
 <div class="sect2">
-<h3 id="client.connections"><a class="anchor" href="#client.connections"></a>65.1. Cluster Connections</h3>
+<h3 id="client.connections"><a class="anchor" href="#client.connections"></a>66.1. Cluster Connections</h3>
 <div class="paragraph">
 <p>The API changed in HBase 1.0. For connection configuration information, see <a href="#client_dependencies">Client configuration and dependencies connecting to an HBase cluster</a>.</p>
 </div>
 <div class="sect3">
-<h4 id="_api_as_of_hbase_1_0_0"><a class="anchor" href="#_api_as_of_hbase_1_0_0"></a>65.1.1. API as of HBase 1.0.0</h4>
+<h4 id="_api_as_of_hbase_1_0_0"><a class="anchor" href="#_api_as_of_hbase_1_0_0"></a>66.1.1. API as of HBase 1.0.0</h4>
 <div class="paragraph">
 <p>It&#8217;s been cleaned up and users are returned Interfaces to work against rather than particular types.
 In HBase 1.0, obtain a <code>Connection</code> object from <code>ConnectionFactory</code> and thereafter, get from it instances of <code>Table</code>, <code>Admin</code>, and <code>RegionLocator</code> on an as-need basis.
@@ -12781,7 +12860,7 @@ See the <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/
 </div>
 </div>
 <div class="sect3">
-<h4 id="_api_before_hbase_1_0_0"><a class="anchor" href="#_api_before_hbase_1_0_0"></a>65.1.2. API before HBase 1.0.0</h4>
+<h4 id="_api_before_hbase_1_0_0"><a class="anchor" href="#_api_before_hbase_1_0_0"></a>66.1.2. API before HBase 1.0.0</h4>
 <div class="paragraph">
 <p>Instances of <code>HTable</code> are the way to interact with an HBase cluster earlier than 1.0.0. <em><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html">Table</a> instances are not thread-safe</em>. Only one thread can use an instance of Table at any given time.
 When creating Table instances, it is advisable to use the same <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/HBaseConfiguration">HBaseConfiguration</a> instance.
@@ -12853,7 +12932,7 @@ Please use <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/clie
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.writebuffer"><a class="anchor" href="#client.writebuffer"></a>65.2. WriteBuffer and Batch Methods</h3>
+<h3 id="client.writebuffer"><a class="anchor" href="#client.writebuffer"></a>66.2. WriteBuffer and Batch Methods</h3>
 <div class="paragraph">
 <p>In HBase 1.0 and later, <a href="http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/client/HTable.html">HTable</a> is deprecated in favor of <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Table.html">Table</a>. <code>Table</code> does not use autoflush. To do buffered writes, use the BufferedMutator class.</p>
 </div>
@@ -12868,7 +12947,7 @@ Please use <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/clie
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.external"><a class="anchor" href="#client.external"></a>65.3. External Clients</h3>
+<h3 id="client.external"><a class="anchor" href="#client.external"></a>66.3. External Clients</h3>
 <div class="paragraph">
 <p>Information on non-Java clients and custom protocols is covered in <a href="#external_apis">Apache HBase External APIs</a></p>
 </div>
@@ -12876,7 +12955,7 @@ Please use <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/clie
 </div>
 </div>
 <div class="sect1">
-<h2 id="client.filter"><a class="anchor" href="#client.filter"></a>66. Client Request Filters</h2>
+<h2 id="client.filter"><a class="anchor" href="#client.filter"></a>67. Client Request Filters</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Get.html">Get</a> and <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/client/Scan.html">Scan</a> instances can be optionally configured with <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/Filter.html">filters</a> which are applied on the RegionServer.</p>
@@ -12885,12 +12964,12 @@ Please use <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/clie
 <p>Filters can be confusing because there are many different types, and it is best to approach them by understanding the groups of Filter functionality.</p>
 </div>
 <div class="sect2">
-<h3 id="client.filter.structural"><a class="anchor" href="#client.filter.structural"></a>66.1. Structural</h3>
+<h3 id="client.filter.structural"><a class="anchor" href="#client.filter.structural"></a>67.1. Structural</h3>
 <div class="paragraph">
 <p>Structural Filters contain other Filters.</p>
 </div>
 <div class="sect3">
-<h4 id="client.filter.structural.fl"><a class="anchor" href="#client.filter.structural.fl"></a>66.1.1. FilterList</h4>
+<h4 id="client.filter.structural.fl"><a class="anchor" href="#client.filter.structural.fl"></a>67.1.1. FilterList</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/FilterList.html">FilterList</a> represents a list of Filters with a relationship of <code>FilterList.Operator.MUST_PASS_ALL</code> or <code>FilterList.Operator.MUST_PASS_ONE</code> between the Filters.
 The following example shows an 'or' between two Filters (checking for either 'my value' or 'my other value' on the same attribute).</p>
@@ -12918,9 +12997,9 @@ scan.setFilter(list);</code></pre>
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.filter.cv"><a class="anchor" href="#client.filter.cv"></a>66.2. Column Value</h3>
+<h3 id="client.filter.cv"><a class="anchor" href="#client.filter.cv"></a>67.2. Column Value</h3>
 <div class="sect3">
-<h4 id="client.filter.cv.scvf"><a class="anchor" href="#client.filter.cv.scvf"></a>66.2.1. SingleColumnValueFilter</h4>
+<h4 id="client.filter.cv.scvf"><a class="anchor" href="#client.filter.cv.scvf"></a>67.2.1. SingleColumnValueFilter</h4>
 <div class="paragraph">
 <p>A SingleColumnValueFilter (see:
 <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.html" class="bare">http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/SingleColumnValueFilter.html</a>)
@@ -12942,13 +13021,13 @@ scan.setFilter(filter);</code></pre>
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.filter.cvp"><a class="anchor" href="#client.filter.cvp"></a>66.3. Column Value Comparators</h3>
+<h3 id="client.filter.cvp"><a class="anchor" href="#client.filter.cvp"></a>67.3. Column Value Comparators</h3>
 <div class="paragraph">
 <p>There are several Comparator classes in the Filter package that deserve special mention.
 These Comparators are used in concert with other Filters, such as <a href="#client.filter.cv.scvf">SingleColumnValueFilter</a>.</p>
 </div>
 <div class="sect3">
-<h4 id="client.filter.cvp.rcs"><a class="anchor" href="#client.filter.cvp.rcs"></a>66.3.1. RegexStringComparator</h4>
+<h4 id="client.filter.cvp.rcs"><a class="anchor" href="#client.filter.cvp.rcs"></a>67.3.1. RegexStringComparator</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/RegexStringComparator.html">RegexStringComparator</a> supports regular expressions for value comparisons.</p>
 </div>
@@ -12969,7 +13048,7 @@ scan.setFilter(filter);</code></pre>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.cvp.substringcomparator"><a class="anchor" href="#client.filter.cvp.substringcomparator"></a>66.3.2. SubstringComparator</h4>
+<h4 id="client.filter.cvp.substringcomparator"><a class="anchor" href="#client.filter.cvp.substringcomparator"></a>67.3.2. SubstringComparator</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/SubstringComparator.html">SubstringComparator</a> can be used to determine if a given substring exists in a value.
 The comparison is case-insensitive.</p>
@@ -12988,38 +13067,38 @@ scan.setFilter(filter);</code></pre>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.cvp.bfp"><a class="anchor" href="#client.filter.cvp.bfp"></a>66.3.3. BinaryPrefixComparator</h4>
+<h4 id="client.filter.cvp.bfp"><a class="anchor" href="#client.filter.cvp.bfp"></a>67.3.3. BinaryPrefixComparator</h4>
 <div class="paragraph">
 <p>See <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/BinaryPrefixComparator.html">BinaryPrefixComparator</a>.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.cvp.bc"><a class="anchor" href="#client.filter.cvp.bc"></a>66.3.4. BinaryComparator</h4>
+<h4 id="client.filter.cvp.bc"><a class="anchor" href="#client.filter.cvp.bc"></a>67.3.4. BinaryComparator</h4>
 <div class="paragraph">
 <p>See <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/BinaryComparator.html">BinaryComparator</a>.</p>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.filter.kvm"><a class="anchor" href="#client.filter.kvm"></a>66.4. KeyValue Metadata</h3>
+<h3 id="client.filter.kvm"><a class="anchor" href="#client.filter.kvm"></a>67.4. KeyValue Metadata</h3>
 <div class="paragraph">
 <p>As HBase stores data internally as KeyValue pairs, KeyValue Metadata Filters evaluate the existence of keys (i.e., ColumnFamily:Column qualifiers) for a row, as opposed to values the previous section.</p>
 </div>
 <div class="sect3">
-<h4 id="client.filter.kvm.ff"><a class="anchor" href="#client.filter.kvm.ff"></a>66.4.1. FamilyFilter</h4>
+<h4 id="client.filter.kvm.ff"><a class="anchor" href="#client.filter.kvm.ff"></a>67.4.1. FamilyFilter</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/FamilyFilter.html">FamilyFilter</a> can be used to filter on the ColumnFamily.
 It is generally a better idea to select ColumnFamilies in the Scan than to do it with a Filter.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.kvm.qf"><a class="anchor" href="#client.filter.kvm.qf"></a>66.4.2. QualifierFilter</h4>
+<h4 id="client.filter.kvm.qf"><a class="anchor" href="#client.filter.kvm.qf"></a>67.4.2. QualifierFilter</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/QualifierFilter.html">QualifierFilter</a> can be used to filter based on Column (aka Qualifier) name.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.kvm.cpf"><a class="anchor" href="#client.filter.kvm.cpf"></a>66.4.3. ColumnPrefixFilter</h4>
+<h4 id="client.filter.kvm.cpf"><a class="anchor" href="#client.filter.kvm.cpf"></a>67.4.3. ColumnPrefixFilter</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/ColumnPrefixFilter.html">ColumnPrefixFilter</a> can be used to filter based on the lead portion of Column (aka Qualifier) names.</p>
 </div>
@@ -13056,7 +13135,7 @@ rs.close();</code></pre>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.kvm.mcpf"><a class="anchor" href="#client.filter.kvm.mcpf"></a>66.4.4. MultipleColumnPrefixFilter</h4>
+<h4 id="client.filter.kvm.mcpf"><a class="anchor" href="#client.filter.kvm.mcpf"></a>67.4.4. MultipleColumnPrefixFilter</h4>
 <div class="paragraph">
 <p><a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/MultipleColumnPrefixFilter.html">MultipleColumnPrefixFilter</a> behaves like ColumnPrefixFilter but allows specifying multiple prefixes.</p>
 </div>
@@ -13089,7 +13168,7 @@ rs.close();</code></pre>
 </div>
 </div>
 <div class="sect3">
-<h4 id="client.filter.kvm.crf"><a class="anchor" href="#client.filter.kvm.crf"></a>66.4.5. ColumnRangeFilter</h4>
+<h4 id="client.filter.kvm.crf"><a class="anchor" href="#client.filter.kvm.crf"></a>67.4.5. ColumnRangeFilter</h4>
 <div class="paragraph">
 <p>A <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/ColumnRangeFilter.html">ColumnRangeFilter</a> allows efficient intra row scanning.</p>
 </div>
@@ -13133,18 +13212,18 @@ rs.close();</code></pre>
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.filter.row"><a class="anchor" href="#client.filter.row"></a>66.5. RowKey</h3>
+<h3 id="client.filter.row"><a class="anchor" href="#client.filter.row"></a>67.5. RowKey</h3>
 <div class="sect3">
-<h4 id="client.filter.row.rf"><a class="anchor" href="#client.filter.row.rf"></a>66.5.1. RowFilter</h4>
+<h4 id="client.filter.row.rf"><a class="anchor" href="#client.filter.row.rf"></a>67.5.1. RowFilter</h4>
 <div class="paragraph">
 <p>It is generally a better idea to use the startRow/stopRow methods on Scan for row selection, however <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/RowFilter.html">RowFilter</a> can also be used.</p>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="client.filter.utility"><a class="anchor" href="#client.filter.utility"></a>66.6. Utility</h3>
+<h3 id="client.filter.utility"><a class="anchor" href="#client.filter.utility"></a>67.6. Utility</h3>
 <div class="sect3">
-<h4 id="client.filter.utility.fkof"><a class="anchor" href="#client.filter.utility.fkof"></a>66.6.1. FirstKeyOnlyFilter</h4>
+<h4 id="client.filter.utility.fkof"><a class="anchor" href="#client.filter.utility.fkof"></a>67.6.1. FirstKeyOnlyFilter</h4>
 <div class="paragraph">
 <p>This is primarily used for rowcount jobs.
 See <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/FirstKeyOnlyFilter.html">FirstKeyOnlyFilter</a>.</p>
@@ -13154,7 +13233,7 @@ See <a href="http://hbase.apache.org/apidocs/org/apache/hadoop/hbase/filter/Firs
 </div>
 </div>
 <div class="sect1">
-<h2 id="architecture.master"><a class="anchor" href="#architecture.master"></a>67. Master</h2>
+<h2 id="architecture.master"><a class="anchor" href="#architecture.master"></a>68. Master</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p><code>HMaster</code> is the implementation of the Master Server.
@@ -13163,14 +13242,14 @@ In a distributed cluster, the Master typically runs on the <a href="#arch.hdfs.n
 J Mohamed Zahoor goes into some more detail on the Master Architecture in this blog posting, <a href="http://blog.zahoor.in/2012/08/hbase-hmaster-architecture/">HBase HMaster Architecture </a>.</p>
 </div>
 <div class="sect2">
-<h3 id="master.startup"><a class="anchor" href="#master.startup"></a>67.1. Startup Behavior</h3>
+<h3 id="master.startup"><a class="anchor" href="#master.startup"></a>68.1. Startup Behavior</h3>
 <div class="paragraph">
 <p>If run in a multi-Master environment, all Masters compete to run the cluster.
 If the active Master loses its lease in ZooKeeper (or the Master shuts down), then the remaining Masters jostle to take over the Master role.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="master.runtime"><a class="anchor" href="#master.runtime"></a>67.2. Runtime Impact</h3>
+<h3 id="master.runtime"><a class="anchor" href="#master.runtime"></a>68.2. Runtime Impact</h3>
 <div class="paragraph">
 <p>A common dist-list question involves what happens to an HBase cluster when the Master goes down.
 Because the HBase client talks directly to the RegionServers, the cluster can still function in a "steady state". Additionally, per <a href="#arch.catalog">Catalog Tables</a>, <code>hbase:meta</code> exists as an HBase table and is not resident in the Master.
@@ -13179,7 +13258,7 @@ So while the cluster can still run for a short time without the Master, the Mast
 </div>
 </div>
 <div class="sect2">
-<h3 id="master.api"><a class="anchor" href="#master.api"></a>67.3. Interface</h3>
+<h3 id="master.api"><a class="anchor" href="#master.api"></a>68.3. Interface</h3>
 <div class="paragraph">
 <p>The methods exposed by <code>HMasterInterface</code> are primarily metadata-oriented methods:</p>
 </div>
@@ -13198,12 +13277,12 @@ So while the cluster can still run for a short time without the Master, the Mast
 </div>
 </div>
 <div class="sect2">
-<h3 id="master.processes"><a class="anchor" href="#master.processes"></a>67.4. Processes</h3>
+<h3 id="master.processes"><a class="anchor" href="#master.processes"></a>68.4. Processes</h3>
 <div class="paragraph">
 <p>The Master runs several background threads:</p>
 </div>
 <div class="sect3">
-<h4 id="master.processes.loadbalancer"><a class="anchor" href="#master.processes.loadbalancer"></a>67.4.1. LoadBalancer</h4>
+<h4 id="master.processes.loadbalancer"><a class="anchor" href="#master.processes.loadbalancer"></a>68.4.1. LoadBalancer</h4>
 <div class="paragraph">
 <p>Periodically, and when there are no regions in transition, a load balancer will run and move regions around to balance the cluster&#8217;s load.
 See <a href="#balancer_config">Balancer</a> for configuring this property.</p>
@@ -13213,7 +13292,7 @@ See <a href="#balancer_config">Balancer</a> for configuring this property.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="master.processes.catalog"><a class="anchor" href="#master.processes.catalog"></a>67.4.2. CatalogJanitor</h4>
+<h4 id="master.processes.catalog"><a class="anchor" href="#master.processes.catalog"></a>68.4.2. CatalogJanitor</h4>
 <div class="paragraph">
 <p>Periodically checks and cleans up the <code>hbase:meta</code> table.
 See &lt;arch.catalog.meta&gt;&gt; for more information on the meta table.</p>
@@ -13223,7 +13302,7 @@ See &lt;arch.catalog.meta&gt;&gt; for more information on the meta table.</p>
 </div>
 </div>
 <div class="sect1">
-<h2 id="regionserver.arch"><a class="anchor" href="#regionserver.arch"></a>68. RegionServer</h2>
+<h2 id="regionserver.arch"><a class="anchor" href="#regionserver.arch"></a>69. RegionServer</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p><code>HRegionServer</code> is the RegionServer implementation.
@@ -13231,7 +13310,7 @@ It is responsible for serving and managing regions.
 In a distributed cluster, a RegionServer runs on a <a href="#arch.hdfs.dn">DataNode</a>.</p>
 </div>
 <div class="sect2">
-<h3 id="regionserver.arch.api"><a class="anchor" href="#regionserver.arch.api"></a>68.1. Interface</h3>
+<h3 id="regionserver.arch.api"><a class="anchor" href="#regionserver.arch.api"></a>69.1. Interface</h3>
 <div class="paragraph">
 <p>The methods exposed by <code>HRegionRegionInterface</code> contain both data-oriented and region-maintenance methods:</p>
 </div>
@@ -13247,37 +13326,37 @@ In a distributed cluster, a RegionServer runs on a <a href="#arch.hdfs.dn">DataN
 </div>
 </div>
 <div class="sect2">
-<h3 id="regionserver.arch.processes"><a class="anchor" href="#regionserver.arch.processes"></a>68.2. Processes</h3>
+<h3 id="regionserver.arch.processes"><a class="anchor" href="#regionserver.arch.processes"></a>69.2. Processes</h3>
 <div class="paragraph">
 <p>The RegionServer runs a variety of background threads:</p>
 </div>
 <div class="sect3">
-<h4 id="regionserver.arch.processes.compactsplit"><a class="anchor" href="#regionserver.arch.processes.compactsplit"></a>68.2.1. CompactSplitThread</h4>
+<h4 id="regionserver.arch.processes.compactsplit"><a class="anchor" href="#regionserver.arch.processes.compactsplit"></a>69.2.1. CompactSplitThread</h4>
 <div class="paragraph">
 <p>Checks for splits and handle minor compactions.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="regionserver.arch.processes.majorcompact"><a class="anchor" href="#regionserver.arch.processes.majorcompact"></a>68.2.2. MajorCompactionChecker</h4>
+<h4 id="regionserver.arch.processes.majorcompact"><a class="anchor" href="#regionserver.arch.processes.majorcompact"></a>69.2.2. MajorCompactionChecker</h4>
 <div class="paragraph">
 <p>Checks for major compactions.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="regionserver.arch.processes.memstore"><a class="anchor" href="#regionserver.arch.processes.memstore"></a>68.2.3. MemStoreFlusher</h4>
+<h4 id="regionserver.arch.processes.memstore"><a class="anchor" href="#regionserver.arch.processes.memstore"></a>69.2.3. MemStoreFlusher</h4>
 <div class="paragraph">
 <p>Periodically flushes in-memory writes in the MemStore to StoreFiles.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="regionserver.arch.processes.log"><a class="anchor" href="#regionserver.arch.processes.log"></a>68.2.4. LogRoller</h4>
+<h4 id="regionserver.arch.processes.log"><a class="anchor" href="#regionserver.arch.processes.log"></a>69.2.4. LogRoller</h4>
 <div class="paragraph">
 <p>Periodically checks the RegionServer&#8217;s WAL.</p>
 </div>
 </div>
 </div>
 <div class="sect2">
-<h3 id="_coprocessors"><a class="anchor" href="#_coprocessors"></a>68.3. Coprocessors</h3>
+<h3 id="_coprocessors"><a class="anchor" href="#_coprocessors"></a>69.3. Coprocessors</h3>
 <div class="paragraph">
 <p>Coprocessors were added in 0.92.
 There is a thorough <a href="https://blogs.apache.org/hbase/entry/coprocessor_introduction">Blog Overview of CoProcessors</a> posted.
@@ -13285,7 +13364,7 @@ Documentation will eventually move to this reference guide, but the blog is the
 </div>
 </div>
 <div class="sect2">
-<h3 id="block.cache"><a class="anchor" href="#block.cache"></a>68.4. Block Cache</h3>
+<h3 id="block.cache"><a class="anchor" href="#block.cache"></a>69.4. Block Cache</h3>
 <div class="paragraph">
 <p>HBase provides two different BlockCache implementations: the default on-heap <code>LruBlockCache</code> and the <code>BucketCache</code>, which is (usually) off-heap.
 This section discusses benefits and drawbacks of each implementation, how to choose the appropriate option, and configuration options for each.</p>
@@ -13307,7 +13386,7 @@ Since HBase 0.98.4, the Block Cache detail has been significantly extended showi
 </table>
 </div>
 <div class="sect3">
-<h4 id="_cache_choices"><a class="anchor" href="#_cache_choices"></a>68.4.1. Cache Choices</h4>
+<h4 id="_cache_choices"><a class="anchor" href="#_cache_choices"></a>69.4.1. Cache Choices</h4>
 <div class="paragraph">
 <p><code>LruBlockCache</code> is the original implementation, and is entirely within the Java heap. <code>BucketCache</code> is mainly intended for keeping block cache data off-heap, although <code>BucketCache</code> can also keep data on-heap and serve from a file-backed cache.</p>
 </div>
@@ -13343,7 +13422,7 @@ See <a href="#offheap.blockcache">Off-heap Block Cache</a> for more detail on go
 </div>
 </div>
 <div class="sect3">
-<h4 id="cache.configurations"><a class="anchor" href="#cache.configurations"></a>68.4.2. General Cache Configurations</h4>
+<h4 id="cache.configurations"><a class="anchor" href="#cache.configurations"></a>69.4.2. General Cache Configurations</h4>
 <div class="paragraph">
 <p>Apart from the cache implementation itself, you can set some general configuration options to control how the cache performs.
 See <a href="http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html" class="bare">http://hbase.apache.org/devapidocs/org/apache/hadoop/hbase/io/hfile/CacheConfig.html</a>.
@@ -13355,7 +13434,7 @@ Check logs for errors or unexpected behavior.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="block.cache.design"><a class="anchor" href="#block.cache.design"></a>68.4.3. LruBlockCache Design</h4>
+<h4 id="block.cache.design"><a class="anchor" href="#block.cache.design"></a>69.4.3. LruBlockCache Design</h4>
 <div class="paragraph">
 <p>The LruBlockCache is an LRU cache that contains three levels of block priority to allow for scan-resistance and in-memory ColumnFamilies:</p>
 </div>
@@ -13397,7 +13476,7 @@ This group is the last one considered during evictions.</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="block.cache.usage"><a class="anchor" href="#block.cache.usage"></a>68.4.4. LruBlockCache Usage</h4>
+<h4 id="block.cache.usage"><a class="anchor" href="#block.cache.usage"></a>69.4.4. LruBlockCache Usage</h4>
 <div class="paragraph">
 <p>Block caching is enabled by default for all the user tables which means that any read operation will load the LRU cache.
 This might be good for a large number of use cases, but further tunings are usually required in order to achieve better performance.
@@ -13496,7 +13575,7 @@ Since <a href="https://issues.apache.org/jira/browse/HBASE-4683">HBASE-4683 Alwa
 </div>
 </div>
 <div class="sect3">
-<h4 id="offheap.blockcache"><a class="anchor" href="#offheap.blockcache"></a>68.4.5. Off-heap Block Cache</h4>
+<h4 id="offheap.blockcache"><a class="anchor" href="#offheap.blockcache"></a>69.4.5. Off-heap Block Cache</h4>
 <div class="sect4">
 <h5 id="enable.bucketcache"><a class="anchor" href="#enable.bucketcache"></a>How to Enable BucketCache</h5>
 <div class="paragraph">
@@ -13648,7 +13727,7 @@ L1 LruBlockCache size is set as a fraction of java heap using <code>hfile.block.
 </div>
 </div>
 <div class="sect3">
-<h4 id="_compressed_blockcache"><a class="anchor" href="#_compressed_blockcache"></a>68.4.6. Compressed BlockCache</h4>
+<h4 id="_compressed_blockcache"><a class="anchor" href="#_compressed_blockcache"></a>69.4.6. Compressed BlockCache</h4>
 <div class="paragraph">
 <p><a href="https://issues.apache.org/jira/browse/HBASE-11331">HBASE-11331</a> introduced lazy BlockCache decompression, more simply referred to as compressed BlockCache.
 When compressed BlockCache is enabled data and encoded data blocks are cached in the BlockCache in their on-disk format, rather than being decompressed and decrypted before caching.</p>
@@ -13663,7 +13742,7 @@ For a RegionServer hosting data that can comfortably fit into cache, or if your
 </div>
 </div>
 <div class="sect2">
-<h3 id="regionserver_splitting_implementation"><a class="anchor" href="#regionserver_splitting_implementation"></a>68.5. RegionServer Splitting Implementation</h3>
+<h3 id="regionserver_splitting_implementation"><a class="anchor" href="#regionserver_splitting_implementation"></a>69.5. RegionServer Splitting Implementation</h3>
 <div class="paragraph">
 <p>As write requests are handled by the region server, they accumulate in an in-memory storage system called the <em>memstore</em>. Once the memstore fills, its content are written to disk as additional store files. This event is called a <em>memstore flush</em>. As store files accumulate, the RegionServer will <a href="#compaction">compact</a> them into fewer, larger files. After each flush or compaction finishes, the amount of data stored in the region has changed. The RegionServer consults the region split policy to determine if the region has grown too large or should be split for another policy-specific reason. A region split request is enqueued if the policy recommends it.</p>
 </div>
@@ -13721,9 +13800,9 @@ Those reference files will point to the parent region&#8217;s files.</p>
 </div>
 </div>
 <div class="sect2">
-<h3 id="wal"><a class="anchor" href="#wal"></a>68.6. Write Ahead Log (WAL)</h3>
+<h3 id="wal"><a class="anchor" href="#wal"></a>69.6. Write Ahead Log (WAL)</h3>
 <div class="sect3">
-<h4 id="purpose.wal"><a class="anchor" href="#purpose.wal"></a>68.6.1. Purpose</h4>
+<h4 id="purpose.wal"><a class="anchor" href="#purpose.wal"></a>69.6.1. Purpose</h4>
 <div class="paragraph">
 <p>The <em>Write Ahead Log (WAL)</em> records all changes to data in HBase, to file-based storage.
 Under normal operations, the WAL is not needed because data changes move from the MemStore to StoreFiles.
@@ -13760,7 +13839,7 @@ You will likely find references to the HLog in documentation tailored to these o
 </div>
 </div>
 <div class="sect3">
-<h4 id="_multiwal"><a class="anchor" href="#_multiwal"></a>68.6.2. MultiWAL</h4>
+<h4 id="_multiwal"><a class="anchor" href="#_multiwal"></a>69.6.2. MultiWAL</h4>
 <div class="paragraph">
 <p>With a single WAL per RegionServer, the RegionServer must write to the WAL serially, because HDFS files must be sequential. This causes the WAL to be a performance bottleneck.</p>
 </div>
@@ -13790,13 +13869,13 @@ You will likely find references to the HLog in documentation tailored to these o
 </div>
 </div>
 <div class="sect3">
-<h4 id="wal_flush"><a class="anchor" href="#wal_flush"></a>68.6.3. WAL Flushing</h4>
+<h4 id="wal_flush"><a class="anchor" href="#wal_flush"></a>69.6.3. WAL Flushing</h4>
 <div class="paragraph">
 <p>TODO (describe).</p>
 </div>
 </div>
 <div class="sect3">
-<h4 id="_wal_splitting"><a class="anchor" href="#_wal_splitting"></a>68.6.4. WAL Splitting</h4>
+<h4 id="_wal_splitting"><a class="anchor" href="#_wal_splitting"></a>69.6.4. WAL Splitting</h4>
 <div class="paragraph">
 <p>A RegionServer serves many regions.
 All of the regions in a region server share the same active WAL file.
@@ -14164,7 +14243,7 @@ See <a href="https://issues.apache.org/jira/browse/HBASE-10855">HBASE-10855</a>)
 </div>
 </div>
 <div class="sect3">
-<h4 id="wal.disable"><a class="anchor" href="#wal.disable"></a>68.6.5. Disabling the WAL</h4>
+<h4 id="wal.disable"><a class="anchor" href="#wal.disable"></a>69.6.5. Disabling the WAL</h4>
 <div class="paragraph">
 <p>It is possible to disable the WAL, to improve performance in certain specific situations.
 However, disabling the WAL puts your data at risk.
@@ -14193,7 +14272,7 @@ If you disable the WAL for anything other than bulk loads, your data is at risk.
 </div>
 </div>
 <div class="sect1">
-<h2 id="regions.arch"><a class="anchor" href="#regions.arch"></a>69. Regions</h2>
+<h2 id="regions.arch"><a class="anchor" href="#regions.arch"></a>70. Regions</h2>
 <div class="sectionbody">
 <div class="paragraph">
 <p>Regions are the basic element of availability and distribution for tables, and are comprised of a Store per Column Family.
@@ -14213,13 +14292,13 @@ The hierarchy of objects is as follows:</p>
 <p>For a description of what HBase files look like when written to HDFS, see <a href="#trouble.namenode.hbase.objects">Browsing HDFS for HBase Objects</a>.</p>
 </div>
 <div class="sect2">
-<h3 id="arch.regions.size"><a class="anchor" href="#arch.regions.size"></a>69.1. Considerations for Number of Regions</h3>
+<h3 id="arch.regions.size"><a class="anchor" href="#arch.regions.size"></a>70.1. Considerations for Number of Regions</h3>
 <div class="paragraph">
 <p>In general, HBase is designed to run with a small (20-200) number of relatively large (5-20Gb) regions per server.
 The considerations for this are as follows:</p>
 </div>
 <div class="sect3">
-<h4 id="too_many_regions"><a class="anchor" href="#too_many_regions"></a>69.1.1. Why should I keep my Region count low?</h4>
+<h4 id="too_many_regions"><a class="anchor" href="#too_

<TRUNCATED>

Mime
View raw message