Repository: hbase Updated Branches: refs/heads/master 8da6f069c -> b31304354
HBASE-18275 Formatting and grammar mistakes in schemadoc chapter (Artem Ervits) Project: http://git-wip-us.apache.org/repos/asf/hbase/repo Commit: http://git-wip-us.apache.org/repos/asf/hbase/commit/b3130435 Tree: http://git-wip-us.apache.org/repos/asf/hbase/tree/b3130435 Diff: http://git-wip-us.apache.org/repos/asf/hbase/diff/b3130435 Branch: refs/heads/master Commit: b3130435424cad356d32a8a92bd2ef60b4d50f00 Parents: 8da6f06 Author: tedyu <yuzhih...@gmail.com> Authored: Tue Jun 27 19:18:02 2017 -0700 Committer: tedyu <yuzhih...@gmail.com> Committed: Tue Jun 27 19:18:02 2017 -0700 ---------------------------------------------------------------------- src/main/asciidoc/_chapters/schema_design.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) ---------------------------------------------------------------------- http://git-wip-us.apache.org/repos/asf/hbase/blob/b3130435/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 7b85d15..acfcdda 100644 --- a/src/main/asciidoc/_chapters/schema_design.adoc +++ b/src/main/asciidoc/_chapters/schema_design.adoc @@ -748,7 +748,7 @@ This approach would be useful if scanning by hostname was a priority. [[schema.casestudies.log_timeseries.revts]] ==== Timestamp, or Reverse Timestamp? -If the most important access path is to pull most recent events, then storing the timestamps as reverse-timestamps (e.g., `timestamp = Long.MAX_VALUE â timestamp`) will create the property of being able to do a Scan on `[hostname][log-event]` to obtain the quickly obtain the most recently captured events. +If the most important access path is to pull most recent events, then storing the timestamps as reverse-timestamps (e.g., `timestamp = Long.MAX_VALUE â timestamp`) will create the property of being able to do a Scan on `[hostname][log-event]` to obtain the most recently captured events. Neither approach is wrong, it just depends on what is most appropriate for the situation. @@ -1152,7 +1152,7 @@ Detect regionserver failure as fast as reasonable. Set the following parameters: - `dfs.client.read.shortcircuit = true` - `dfs.client.read.shortcircuit.buffer.size = 131072` (Important to avoid OOME) * Ensure data locality. In `hbase-site.xml`, set `hbase.hstore.min.locality.to.skip.major.compact = 0.7` (Meaning that 0.7 \<= n \<= 1) -* Make sure DataNodes have enough handlers for block transfers. In `hdfs-site`.xml``, set the following parameters: +* Make sure DataNodes have enough handlers for block transfers. In `hdfs-site.xml`, set the following parameters: - `dfs.datanode.max.xcievers >= 8192` - `dfs.datanode.handler.count =` number of spindles