cleanup, titles

Author: polyfractal

500_Cluster_Admin.asciidoc

@@ -1,5 +1,4 @@
 [[cluster-admin]]
-== Cluster management and monitoring
 include::500_Cluster_Admin/10_intro.asciidoc[]
 
 include::500_Cluster_Admin/15_marvel.asciidoc[]
@@ -9,21 +8,3 @@ include::500_Cluster_Admin/20_health.asciidoc[]
 include::500_Cluster_Admin/30_node_stats.asciidoc[]
 
 include::500_Cluster_Admin/40_other_stats.asciidoc[]
-
-- management
-  - cluster settings
-    - dynamically changing logging
-  - index settings
-  
-
-- monitoring
- - marvel
- - cluster health
- - cluster stats
- - node stats / node info
-    - rejections
- - index stats
- - hot threads
- - pending tasks
-
-- cat api

500_Cluster_Admin/10_intro.asciidoc

@@ -1,6 +1,5 @@
 
-
-
+== Cluster management and monitoring
 Elasticsearch is often deployed as a cluster of nodes.  There are a variety of
 APIs that let you manage and monitor the cluster itself, rather than interact
 with the data stored within the cluster.

500_Cluster_Admin/15_marvel.asciidoc

@@ -1,5 +1,5 @@
 
-=== Marvel for Monitoring
+== Marvel for Monitoring
 
 At the very beginning of the book (<<marvel>>) we encouraged you to install
 Marvel, a management monitoring tool for Elasticsearch, because it would enable

500_Cluster_Admin/20_health.asciidoc

@@ -1,5 +1,5 @@
 
-=== Cluster Health
+== Cluster Health
 
 An Elasticsearch cluster may consist of a single node with a single index.  Or it
 may have a hundred data nodes, three dedicated masters, a few dozen clients nodes
@@ -73,7 +73,7 @@ replicas.  For example, an index with 5 shards and 1 replica will have 5 unassig
 replicas in a single-node cluster.  Unassigned shards will also be present if your
 cluster is red (since primaries are missing)
 
-==== Drilling deeper: finding problematic indices
+=== Drilling deeper: finding problematic indices
 
 Imagine something goes wrong one day, and you notice that your cluster health
 looks like this:
@@ -185,7 +185,7 @@ but due to the verbosity can difficult to work with.  Once you know the index
 that is having problems, other APIs that we discuss in this chapter will tend 
 to be more helpful.
 
-==== Blocking for status changes
+=== Blocking for status changes
 
 The Cluster Health API has another neat trick which is very useful when building
 unit and integration tests, or automated scripts that work with Elasticsearch.

500_Cluster_Admin/30_node_stats.asciidoc

@@ -1,5 +1,5 @@
 
-=== Monitoring individual nodes
+== Monitoring individual nodes
 
 Cluster Health is at one end of the spectrum -- a very high-level overview of
 everything in your cluster.  The _Node Stats_ API is at the other end.  It provides
@@ -43,7 +43,7 @@ host, etc).  These values are useful for debugging discovery problems, where
 nodes won't join the cluster.  Often you'll see that the port being used is wrong,
 or the node is binding to the wrong IP address/interface.
 
-==== Indices section
+=== Indices section
 
 The indices section lists aggregate statistics for all the indices that reside
 on this particular node.
@@ -206,7 +206,7 @@ posting lists, dictionaries and bloom filters.  A very large number of segments
 will increase the amount of overhead lost to these data structures, and the memory
 usage can be a handy metric to gauge that overhead.
 
-==== OS and Process Sections
+=== OS and Process Sections
 
 The OS and Process sections are fairly self-explanatory and won't be covered
 in great detail.  They list basic resource statistics such as CPU and load.  The
@@ -222,7 +222,7 @@ monitoring stack. Some stats include:
 - Swap usage
 - Open file descriptors
 
-==== JVM Section
+=== JVM Section
 
 The JVM section contains some critical information about the JVM process which
 is running Elasticsearch.  Most importantly, it contains garbage collection details,
@@ -390,7 +390,7 @@ Our best advice is to collect collection counts and duration periodically (or us
 and keep an eye out for frequent GCs.  You can also enable slow-GC logging,
 discussed in <<TODO>>
 
-==== Threadpool Section
+=== Threadpool Section
 
 Elasticsearch maintains a number of threadpools internally.  These threadpools
 cooperate to get work done, passing work between each other as necessary. In
@@ -468,7 +468,7 @@ are good to keep an eye on:
 - `search`: all search and query requests
 - `merging`: threadpool dedicated to managing Lucene merges
 
-==== FS and Network sections
+=== FS and Network sections
 
 Continuing down the Node Stats API, you'll see a bunch of statistics about your
 filesystem:  free space, data directory paths, disk IO stats, etc.  If you are
@@ -508,7 +508,7 @@ keep-alive connections are important for performance, since building up and tear
 down sockets is expensive (and wastes file descriptors).  Make sure your clients
 are configured appropriately.
 
-==== Circuit Breaker 
+=== Circuit Breaker 
 
 Finally, we come to the last section: stats about the field data circuit breaker 
 (introduced in <<circuit_breaker>>):

500_Cluster_Admin/40_other_stats.asciidoc

@@ -1,5 +1,5 @@
 
-=== Cluster Stats
+== Cluster Stats
 
 The _Cluster Stats_ API provides very similar output to the Node Stats.  There
 is one crucial difference: Node Stats shows you statistics per-node, while
@@ -19,7 +19,7 @@ The API may be invoked with:
 GET _cluster/stats
 ----
 
-=== Index Stats
+== Index Stats
 
 So far, we have been looking at _node-centric_ statistics.  How much memory does 
 this node have?  How much CPU is being used?  How many searches is this node
@@ -60,7 +60,7 @@ operating in different environments.
 Index-centric stats are a useful tool to keep in your repertoire, but are not usually
 the first tool to reach for.
 
-=== Pending Tasks
+== Pending Tasks
 
 There are certain tasks that only the master can perform, such as creating a new 
 index or moving shards around the cluster.  Since a cluster can only have one
@@ -154,7 +154,7 @@ cluster state size.
 - Spin up another cluster once a certain threshold has been crossed.
 ****
 
-==== Cat API
+=== Cat API
 
 If you work from the command line often, the _Cat_ APIs will be very helpful
 to you.  Named after the linux `cat` command, these APIs are designed to be