Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id DC1DD200B7B for ; Thu, 25 Aug 2016 20:25:15 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id DA9F7160ABE; Thu, 25 Aug 2016 18:25:15 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0ADA2160ACB for ; Thu, 25 Aug 2016 20:25:14 +0200 (CEST) Received: (qmail 19903 invoked by uid 500); 25 Aug 2016 18:25:12 -0000 Mailing-List: contact commits-help@hbase.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@hbase.apache.org Delivered-To: mailing list commits@hbase.apache.org Received: (qmail 19374 invoked by uid 99); 25 Aug 2016 18:25:12 -0000 Received: from git1-us-west.apache.org (HELO git1-us-west.apache.org) (140.211.11.23) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 25 Aug 2016 18:25:12 +0000 Received: by git1-us-west.apache.org (ASF Mail Server at git1-us-west.apache.org, from userid 33) id 3524EEEE7C; Thu, 25 Aug 2016 18:25:12 +0000 (UTC) Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit From: misty@apache.org To: commits@hbase.apache.org Date: Thu, 25 Aug 2016 18:25:26 -0000 Message-Id: <60564095e1124b9e81774342b05ab2fd@git.apache.org> In-Reply-To: <92cfc475fdfb41bb906e7cf367e608c6@git.apache.org> References: <92cfc475fdfb41bb906e7cf367e608c6@git.apache.org> X-Mailer: ASF-Git Admin Mailer Subject: [16/51] [abbrv] [partial] hbase-site git commit: Published site at 44c9021d67b0e922e1d2f5f53908742aceab6c80. archived-at: Thu, 25 Aug 2016 18:25:16 -0000 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

4.1.4. Hadoop versions 0.20.x - 1.x

-

HBase will lose data unless it is running on an HDFS that has a durable sync 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 An - update on Apache Hadoop 1.0 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.

-
-
-

Sync has to be explicitly enabled by setting dfs.support.append equal to true on both the client side — in hbase-site.xml — and on the serverside in hdfs-site.xml (The sync facility HBase needs is a subset of the append code path).

-
-
-
-
<property>
-  <name>dfs.support.append</name>
-  <value>true</value>
-</property>
-
-
-
-

You will have to restart your cluster after making this edit. -Ignore the chicken-little comment you’ll find in the hdfs-default.xml in the description for the dfs.support.append configuration.

+

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.

@@ -4827,6 +4807,21 @@ Configuration that it is thought rare anyone would change can exist only in code
+
+
+
hbase.serial.replication.waitingMs
+
+
+
Description
+

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.

+
+
+
Default
+

10000

+
+
+
+
hbase.http.staticuser.user
@@ -5876,13 +5871,16 @@ It may be possible to skip across versions — for example go fr

Allow changing or removing existing client APIs.

  • -

    An API needs to deprecated for a major version before we will change/remove it.

    +

    An API needs to be deprecated for a major version before we will change/remove it.

  • 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.

  • -

    Example: A user using a newly deprecated api does not need to modify application code with hbase api calls until the next major version.

    +

    New APIs introduced in a patch version will only be added in a source compatible way [1]: i.e. code that implements public APIs will continue to compile.

    +
    • +
  • +

    Example: A user using a newly deprecated API does not need to modify application code with HBase API calls until the next major version.

    • @@ -5943,7 +5941,7 @@ It may be possible to skip across versions — for example go fr
    Summary
    • -

      A patch upgrade is a drop-in replacement. Any change that is not Java binary compatible would not be allowed.[1]. Downgrading versions within patch releases may not be compatible.

      +

      A patch upgrade is a drop-in replacement. Any change that is not Java binary and source compatible would not be allowed.[2] Downgrading versions within patch releases may not be compatible.

    • 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.

      @@ -5954,7 +5952,7 @@ It may be possible to skip across versions — for example go fr
    - +@@ -5982,7 +5980,7 @@ It may be possible to skip across versions — for example go fr - + @@ -24940,7 +24938,7 @@ In this case, or if you are in a OLAP environment and require having locality, t

    HBase emits metrics which adhere to the Hadoop metrics API. -Starting with HBase 0.95[4], HBase is configured to emit a default set of metrics with a default sampling period of every 10 seconds. +Starting with HBase 0.95[5], 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.

    @@ -34050,16 +34048,19 @@ The server will return cellblocks compressed using this same compressor as long
    -1. See http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html. +1. See 'Source Compatibility' https://blogs.oracle.com/darcy/entry/kinds_of_compatibility
    -2. Note that this indicates what could break, not that it will break. We will/should add specifics in our release notes. +2. See http://docs.oracle.com/javase/specs/jls/se7/html/jls-13.html.
    -3. 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. +3. Note that this indicates what could break, not that it will break. We will/should add specifics in our release notes.
    -4. The Metrics system was redone in HBase 0.96. See Migration to the New Metrics Hotness – Metrics2 by Elliot Clark for detail +4. 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. +
    +
    +5. The Metrics system was redone in HBase 0.96. See Migration to the New Metrics Hotness – Metrics2 by Elliot Clark for detail
    Table 3. Compatibility Matrix [2]Table 3. Compatibility Matrix [3]

    File Format Compatibility

    N [3]

    N [4]

    Y

    Y