lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [3/4] lucene-solr:master: Ref Guide: standardize section titles to use headline case
Date Fri, 10 Aug 2018 17:32:53 GMT
Ref Guide: standardize section titles to use headline case


Branch: refs/heads/master
Commit: dfb33e97d04c7de8395bf4d273730ebc0e8141cf
Parents: e46c6b8
Author: Cassandra Targett <>
Authored: Thu Aug 9 13:39:00 2018 -0500
Committer: Cassandra Targett <>
Committed: Fri Aug 10 08:54:43 2018 -0500

 solr/solr-ref-guide/src/cloud-screens.adoc                | 10 +++++-----
 solr/solr-ref-guide/src/coreadmin-api.adoc                |  8 ++++----
 .../src/solrcloud-query-routing-and-read-tolerance.adoc   |  4 ++--
 3 files changed, 11 insertions(+), 11 deletions(-)
diff --git a/solr/solr-ref-guide/src/cloud-screens.adoc b/solr/solr-ref-guide/src/cloud-screens.adoc
index cc5a5eb..28160dd 100644
--- a/solr/solr-ref-guide/src/cloud-screens.adoc
+++ b/solr/solr-ref-guide/src/cloud-screens.adoc
@@ -28,26 +28,26 @@ The "Cloud" menu option is only available on Solr instances running in
 Click on the "Cloud" option in the left-hand navigation, and a small sub-menu appears with
options called "Nodes", "Tree", "Graph" and "Graph (Radial)". The sub-view selected by default
is "Graph".
-== Nodes view
+== Nodes View
 The "Nodes" view shows a list of the hosts and nodes in the cluster along with key information
for each: "CPU", "Heap", "Disk usage", "Requests", "Collections" and "Replicas".
 The example below shows the default "cloud" example with some documents added to the "gettingstarted"
collection. Details are expanded for node on port 7574, showing more metadata and more metrics
details. The screen provides links to navigate to nodes, collections and replicas. The table
supports paging and filtering on host/node names and collection names.
-== Tree view
+== Tree View
 The "Tree" view shows a directory structure of the data in ZooKeeper, including cluster wide
information regarding the `live_nodes` and `overseer` status, as well as collection specific
information such as the `state.json`, current shard leaders, and configuration files in use.
In this example, we see part of the `state.json`  definition for the "tlog" collection:
 As an aid to debugging, the data shown in the "Tree" view can be exported locally using the
following command `bin/solr zk ls -r /`
-== ZK Status view
+== ZK Status View
 The "ZK Status" view gives an overview over the Zookeepers used by Solr. It lists whether
running in `standalone` or `ensemble` mode, shows how many zookeepers are configured, and
then displays a table listing detailed monitoring status for each of the zookeepers, inlcuding
who is the leader, configuration parameters and more.
-== Graph views
+== Graph Views
 The "Graph" view shows a graph of each collection, the shards that make up those collections,
and the addresses and type ("NRT", "TLOG" or "PULL") of each replica for each shard.
 This example shows a simple cluster. In addition to the 2 shard, 2 replica "gettingstarted"
collection, there is an additional "tlog" collection consisting of mixed TLOG and PULL replica
diff --git a/solr/solr-ref-guide/src/coreadmin-api.adoc b/solr/solr-ref-guide/src/coreadmin-api.adoc
index 1b486cd..49895fd 100644
--- a/solr/solr-ref-guide/src/coreadmin-api.adoc
+++ b/solr/solr-ref-guide/src/coreadmin-api.adoc
@@ -269,28 +269,28 @@ Request ID to track this action which will be processed asynchronously.
 The `core` index will be split into as many pieces as the number of `path` or `targetCore`
-==== Usage with two targetCore parameters:
+*Usage with two targetCore parameters*:
 Here the `core` index will be split into two pieces and merged into the two `targetCore`
-==== Usage with two path parameters:
+*Usage with two path parameters*:
 The `core` index will be split into two pieces and written into the two directory paths specified.
-==== Usage with the split.key parameter:
+*Usage with the split.key parameter*:
 Here all documents having the same route key as the `split.key` i.e., 'A!' will be split
from the `core` index and written to the `targetCore`.
-==== Usage with ranges parameter:
+*Usage with ranges parameter*:
diff --git a/solr/solr-ref-guide/src/solrcloud-query-routing-and-read-tolerance.adoc b/solr/solr-ref-guide/src/solrcloud-query-routing-and-read-tolerance.adoc
index a3afbad..d6c4fe4 100644
--- a/solr/solr-ref-guide/src/solrcloud-query-routing-and-read-tolerance.adoc
+++ b/solr/solr-ref-guide/src/solrcloud-query-routing-and-read-tolerance.adoc
@@ -115,7 +115,7 @@ http://localhost:8983/solr/collection1/select?q=*:*&_route_=user1!
-== Distributed tracing and debugging parameters
+== Distributed Tracing and Debugging Parameters
 There are several distributed tracing parameters which can be used to trace the request as
well as find timing information for a distributed request.
@@ -125,7 +125,7 @@ There are several distributed tracing parameters which can be used to
trace the
 |debug=track | Gives debug information for each phase of the distributed query.
-== Optimizations and related parameters
+== Optimizations and Related Parameters
 The table below summarizes the general parameters for controlling routing.

View raw message