hbase-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mi...@apache.org
Subject hbase git commit: HBASE-18635 Fixed Asciidoc warning
Date Fri, 25 Aug 2017 20:10:11 GMT
Repository: hbase
Updated Branches:
  refs/heads/master 2e8739623 -> 368591dfc


HBASE-18635 Fixed Asciidoc warning

Signed-off-by: Misty Stanley-Jones <misty@apache.org>


Project: http://git-wip-us.apache.org/repos/asf/hbase/repo
Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/368591df
Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/368591df
Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/368591df

Branch: refs/heads/master
Commit: 368591dfcd1fb4ec2be480b0970466386b059b82
Parents: 2e87396
Author: Jan Hentschel <jan.hentschel@ultratendency.com>
Authored: Sun Aug 20 23:47:11 2017 +0200
Committer: Misty Stanley-Jones <misty@apache.org>
Committed: Fri Aug 25 13:09:57 2017 -0700

----------------------------------------------------------------------
 src/main/asciidoc/_chapters/external_apis.adoc | 15 +++++++--------
 src/main/asciidoc/_chapters/schema_design.adoc | 12 ++++++------
 2 files changed, 13 insertions(+), 14 deletions(-)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/hbase/blob/368591df/src/main/asciidoc/_chapters/external_apis.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/_chapters/external_apis.adoc b/src/main/asciidoc/_chapters/external_apis.adoc
index 2f85461..c0e4a5f 100644
--- a/src/main/asciidoc/_chapters/external_apis.adoc
+++ b/src/main/asciidoc/_chapters/external_apis.adoc
@@ -288,18 +288,17 @@ your filter to the file. For example, to return only rows for
 which keys start with <codeph>u123</codeph> and use a batch size
 of 100, the filter file would look like this:
 
-+++
-<pre>
-&lt;Scanner batch="100"&gt;
-  &lt;filter&gt;
+[source,xml]
+----
+<Scanner batch="100">
+  <filter>
     {
       "type": "PrefixFilter",
       "value": "u123"
     }
-  &lt;/filter&gt;
-&lt;/Scanner&gt;
-</pre>
-+++
+  </filter>
+</Scanner>
+----
 
 Pass the file to the `-d` argument of the `curl` request.
 |curl -vi -X PUT \

http://git-wip-us.apache.org/repos/asf/hbase/blob/368591df/src/main/asciidoc/_chapters/schema_design.adoc
----------------------------------------------------------------------
diff --git a/src/main/asciidoc/_chapters/schema_design.adoc b/src/main/asciidoc/_chapters/schema_design.adoc
index cef05f2..d17f06b 100644
--- a/src/main/asciidoc/_chapters/schema_design.adoc
+++ b/src/main/asciidoc/_chapters/schema_design.adoc
@@ -1113,7 +1113,7 @@ If you don't have time to build it both ways and compare, my advice
would be to
 [[schema.ops]]
 == Operational and Performance Configuration Options
 
-====  Tune HBase Server RPC Handling
+===  Tune HBase Server RPC Handling
 
 * Set `hbase.regionserver.handler.count` (in `hbase-site.xml`) to cores x spindles for concurrency.
 * Optionally, split the call queues into separate read and write queues for differentiated
service. The parameter `hbase.ipc.server.callqueue.handler.factor` specifies the number of
call queues:
@@ -1129,7 +1129,7 @@ If you don't have time to build it both ways and compare, my advice
would be to
 - `< 0.5` for more short-read
 - `> 0.5` for more long-read
 
-====  Disable Nagle for RPC
+===  Disable Nagle for RPC
 
 Disable Nagle’s algorithm. Delayed ACKs can add up to ~200ms to RPC round trip time. Set
the following parameters:
 
@@ -1140,7 +1140,7 @@ Disable Nagle’s algorithm. Delayed ACKs can add up to ~200ms to RPC
round trip
 - `hbase.ipc.client.tcpnodelay = true`
 - `hbase.ipc.server.tcpnodelay = true`
 
-====  Limit Server Failure Impact
+===  Limit Server Failure Impact
 
 Detect regionserver failure as fast as reasonable. Set the following parameters:
 
@@ -1149,7 +1149,7 @@ Detect regionserver failure as fast as reasonable. Set the following
parameters:
 - `dfs.namenode.avoid.read.stale.datanode = true`
 - `dfs.namenode.avoid.write.stale.datanode = true`
 
-====  Optimize on the Server Side for Low Latency
+===  Optimize on the Server Side for Low Latency
 
 * Skip the network for local blocks. In `hbase-site.xml`, set the following parameters:
 - `dfs.client.read.shortcircuit = true`
@@ -1187,7 +1187,7 @@ Detect regionserver failure as fast as reasonable. Set the following
parameters:
 
 ==  Special Cases
 
-====  For applications where failing quickly is better than waiting
+===  For applications where failing quickly is better than waiting
 
 *  In `hbase-site.xml` on the client side, set the following parameters:
 - Set `hbase.client.pause = 1000`
@@ -1196,7 +1196,7 @@ Detect regionserver failure as fast as reasonable. Set the following
parameters:
 - Set the RecoverableZookeeper retry count: `zookeeper.recovery.retry = 1` (no retry)
 * In `hbase-site.xml` on the server side, set the Zookeeper session timeout for detecting
server failures: `zookeeper.session.timeout` <= 30 seconds (20-30 is good).
 
-====  For applications that can tolerate slightly out of date information
+===  For applications that can tolerate slightly out of date information
 
 **HBase timeline consistency (HBASE-10070) **
 With read replicas enabled, read-only copies of regions (replicas) are distributed over the
cluster. One RegionServer services the default or primary replica, which is the only replica
that can service writes. Other RegionServers serve the secondary replicas, follow the primary
RegionServer, and only see committed updates. The secondary replicas are read-only, but can
serve reads immediately while the primary is failing over, cutting read availability blips
from seconds to milliseconds. Phoenix supports timeline consistency as of 4.4.0


Mime
View raw message