You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@hbase.apache.org by mi...@apache.org on 2016/08/25 18:25:26 UTC
[16/51] [abbrv] [partial] hbase-site git commit: Published site at
44c9021d67b0e922e1d2f5f53908742aceab6c80.
http://git-wip-us.apache.org/repos/asf/hbase-site/blob/a16749a7/book.html
----------------------------------------------------------------------
diff --git a/book.html b/book.html
index 5814bf7..13103c6 100644
--- a/book.html
+++ b/book.html
@@ -1875,27 +1875,7 @@ Do not move to Apache HBase 0.96.x if you cannot upgrade your Hadoop. See <a hre
<div class="sect3">
<h4 id="hadoop.older.versions"><a class="anchor" href="#hadoop.older.versions"></a>4.1.4. Hadoop versions 0.20.x - 1.x</h4>
<div class="paragraph">
-<p>HBase will lose data unless it is running on an HDFS that has a durable <code>sync</code> implementation.
-DO NOT use Hadoop 0.20.2, Hadoop 0.20.203.0, and Hadoop 0.20.204.0 which DO NOT have this attribute.
-Currently only Hadoop versions 0.20.205.x or any release in excess of this version — this includes hadoop-1.0.0 — have a working, durable sync.
-The Cloudera blog post <a href="https://blog.cloudera.com/blog/2012/01/an-update-on-apache-hadoop-1-0/">An
- update on Apache Hadoop 1.0</a> by Charles Zedlweski has a nice exposition on how all the Hadoop versions relate.
-It’s worth checking out if you are having trouble making sense of the Hadoop version morass.</p>
-</div>
-<div class="paragraph">
-<p>Sync has to be explicitly enabled by setting <code>dfs.support.append</code> equal to true on both the client side — in <em>hbase-site.xml</em> — and on the serverside in <em>hdfs-site.xml</em> (The sync facility HBase needs is a subset of the append code path).</p>
-</div>
-<div class="listingblock">
-<div class="content">
-<pre class="CodeRay highlight"><code data-lang="xml"><span class="tag"><property></span>
- <span class="tag"><name></span>dfs.support.append<span class="tag"></name></span>
- <span class="tag"><value></span>true<span class="tag"></value></span>
-<span class="tag"></property></span></code></pre>
-</div>
-</div>
-<div class="paragraph">
-<p>You will have to restart your cluster after making this edit.
-Ignore the chicken-little comment you’ll find in the <em>hdfs-default.xml</em> in the description for the <code>dfs.support.append</code> configuration.</p>
+<p>DO NOT use Hadoop versions older than 2.2.0 for HBase versions greater than 1.0. Check release documentation if you are using an older version of HBase for Hadoop related information.</p>
</div>
</div>
<div class="sect3">
@@ -4827,6 +4807,21 @@ Configuration that it is thought rare anyone would change can exist only in code
</dd>
</dl>
</div>
+<div id="hbase.serial.replication.waitingMs" class="dlist">
+<dl>
+<dt class="hdlist1"><code>hbase.serial.replication.waitingMs</code></dt>
+<dd>
+<div class="paragraph">
+<div class="title">Description</div>
+<p>By default, in replication we can not make sure the order of operations in slave cluster is same as the order in master. If set REPLICATION_SCOPE to 2, we will push edits by the order of written. This configure is to set how long (in ms) we will wait before next checking if a log can not push right now because there are some logs written before it have not been pushed. A larger waiting will decrease the number of queries on hbase:meta but will enlarge the delay of replication. This feature relies on zk-less assignment, and conflicts with distributed log replay. So users must set hbase.assignment.usezk and hbase.master.distributed.log.replay to false to support it.</p>
+</div>
+<div class="paragraph">
+<div class="title">Default</div>
+<p><code>10000</code></p>
+</div>
+</dd>
+</dl>
+</div>
<div id="hbase.http.staticuser.user" class="dlist">
<dl>
<dt class="hdlist1"><code>hbase.http.staticuser.user</code></dt>
@@ -5876,13 +5871,16 @@ It may be possible to skip across versions — for example go fr
<p>Allow changing or removing existing client APIs.</p>
</li>
<li>
-<p>An API needs to deprecated for a major version before we will change/remove it.</p>
+<p>An API needs to be deprecated for a major version before we will change/remove it.</p>
</li>
<li>
<p>APIs available in a patch version will be available in all later patch versions. However, new APIs may be added which will not be available in earlier patch versions.</p>
</li>
<li>
-<p>Example: A user using a newly deprecated api does not need to modify application code with hbase api calls until the next major version.</p>
+<p>New APIs introduced in a patch version will only be added in a source compatible way <span class="footnote">[<a id="_footnoteref_1" class="footnote" href="#_footnote_1" title="View footnote.">1</a>]</span>: i.e. code that implements public APIs will continue to compile.</p>
+</li>
+<li>
+<p>Example: A user using a newly deprecated API does not need to modify application code with HBase API calls until the next major version.</p>
</li>
</ul>
</div>
@@ -5943,7 +5941,7 @@ It may be possible to skip across versions — for example go fr
<div class="title">Summary</div>
<ul>
<li>
-<p>A patch upgrade is a drop-in replacement. Any change that is not Java binary compatible would not be allowed.<span class="footnote">[<a id="_footnoteref_1" class="footnote" href="#_footnote_1" title="View footnote.">1</a>]</span>. Downgrading versions within patch releases may not be compatible.</p>
+<p>A patch upgrade is a drop-in replacement. Any change that is not Java binary and source compatible would not be allowed.<span class="footnote">[<a id="_footnoteref_2" class="footnote" href="#_footnote_2" title="View footnote.">2</a>]</span> Downgrading versions within patch releases may not be compatible.</p>
</li>
<li>
<p>A minor upgrade requires no application/client code modification. Ideally it would be a drop-in replacement but client code, coprocessors, filters, etc might have to be recompiled if new jars are used.</p>
@@ -5954,7 +5952,7 @@ It may be possible to skip across versions — for example go fr
</ul>
</div>
<table class="tableblock frame-all grid-all spread">
-<caption class="title">Table 3. Compatibility Matrix <span class="footnote">[<a id="_footnoteref_2" class="footnote" href="#_footnote_2" title="View footnote.">2</a>]</span></caption>
+<caption class="title">Table 3. Compatibility Matrix <span class="footnote">[<a id="_footnoteref_3" class="footnote" href="#_footnote_3" title="View footnote.">3</a>]</span></caption>
<colgroup>
<col style="width: 25%;">
<col style="width: 25%;">
@@ -5982,7 +5980,7 @@ It may be possible to skip across versions — for example go fr
</tr>
<tr>
<td class="tableblock halign-left valign-top"><p class="tableblock">File Format Compatibility</p></td>
-<td class="tableblock halign-left valign-top"><p class="tableblock">N <span class="footnote">[<a id="_footnoteref_3" class="footnote" href="#_footnote_3" title="View footnote.">3</a>]</span></p></td>
+<td class="tableblock halign-left valign-top"><p class="tableblock">N <span class="footnote">[<a id="_footnoteref_4" class="footnote" href="#_footnote_4" title="View footnote.">4</a>]</span></p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Y</p></td>
<td class="tableblock halign-left valign-top"><p class="tableblock">Y</p></td>
</tr>
@@ -24940,7 +24938,7 @@ In this case, or if you are in a OLAP environment and require having locality, t
<div class="sectionbody">
<div class="paragraph">
<p>HBase emits metrics which adhere to the <a href="http://hadoop.apache.org/core/docs/current/api/org/apache/hadoop/metrics/package-summary.html">Hadoop metrics</a> API.
-Starting with HBase 0.95<span class="footnote">[<a id="_footnoteref_4" class="footnote" href="#_footnote_4" title="View footnote.">4</a>]</span>, HBase is configured to emit a default set of metrics with a default sampling period of every 10 seconds.
+Starting with HBase 0.95<span class="footnote">[<a id="_footnoteref_5" class="footnote" href="#_footnote_5" title="View footnote.">5</a>]</span>, HBase is configured to emit a default set of metrics with a default sampling period of every 10 seconds.
You can use HBase metrics in conjunction with Ganglia.
You can also filter which metrics are emitted and extend the metrics framework to capture custom metrics appropriate for your environment.</p>
</div>
@@ -34050,16 +34048,19 @@ The server will return cellblocks compressed using this same compressor as long
<div id="footnotes">
<hr>
<div class="footnote" id="_footnote_1">
-<a href="#_footnoteref_1">1</a>. See <a href="http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html" class="bare">http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html</a>.
+<a href="#_footnoteref_1">1</a>. See 'Source Compatibility' <a href="https://blogs.oracle.com/darcy/entry/kinds_of_compatibility" class="bare">https://blogs.oracle.com/darcy/entry/kinds_of_compatibility</a>
</div>
<div class="footnote" id="_footnote_2">
-<a href="#_footnoteref_2">2</a>. Note that this indicates what could break, not that it will break. We will/should add specifics in our release notes.
+<a href="#_footnoteref_2">2</a>. See <a href="http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html" class="bare">http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html</a>.
</div>
<div class="footnote" id="_footnote_3">
-<a href="#_footnoteref_3">3</a>. comp_matrix_offline_upgrade_note,Running an offline upgrade tool without rollback might be needed. We will typically only support migrating data from major version X to major version X+1.
+<a href="#_footnoteref_3">3</a>. Note that this indicates what could break, not that it will break. We will/should add specifics in our release notes.
</div>
<div class="footnote" id="_footnote_4">
-<a href="#_footnoteref_4">4</a>. The Metrics system was redone in HBase 0.96. See Migration to the New Metrics Hotness \u2013 Metrics2 by Elliot Clark for detail
+<a href="#_footnoteref_4">4</a>. comp_matrix_offline_upgrade_note,Running an offline upgrade tool without rollback might be needed. We will typically only support migrating data from major version X to major version X+1.
+</div>
+<div class="footnote" id="_footnote_5">
+<a href="#_footnoteref_5">5</a>. The Metrics system was redone in HBase 0.96. See Migration to the New Metrics Hotness \u2013 Metrics2 by Elliot Clark for detail
</div>
</div>
<div id="footer">
http://git-wip-us.apache.org/repos/asf/hbase-site/blob/a16749a7/bulk-loads.html
----------------------------------------------------------------------
diff --git a/bulk-loads.html b/bulk-loads.html
index d320353..d0c73fb 100644
--- a/bulk-loads.html
+++ b/bulk-loads.html
@@ -7,7 +7,7 @@
<head>
<meta charset="UTF-8" />
<meta name="viewport" content="width=device-width, initial-scale=1.0" />
- <meta name="Date-Revision-yyyymmdd" content="20160807" />
+ <meta name="Date-Revision-yyyymmdd" content="20160825" />
<meta http-equiv="Content-Language" content="en" />
<title>Apache HBase –
Bulk Loads in Apache HBase (TM)
@@ -305,7 +305,7 @@ under the License. -->
<a href="http://www.apache.org/">The Apache Software Foundation</a>.
All rights reserved.
- <li id="publishDate" class="pull-right">Last Published: 2016-08-07</li>
+ <li id="publishDate" class="pull-right">Last Published: 2016-08-25</li>
</p>
</div>