anchor.diff:  | Endpoint                           | Instance State  | Returned Code  | Body text
   1.2+^.^| /db/manage/server/ha/master | Master          | 200 OK         | true
                                        | Slave           | 404 Not Found  | false
  +                                     | Unknown         | 404 Not Found  | UNKNOWN
   1.2+^.^| /db/manage/server/ha/slave  | Master          | 404 Not Found  | false
                                        | Slave           | 200 OK         | true
  +                                     | Unknown         | 404 Not Found  | UNKNOWN
   |========================================================================================
   
   
  
positive.code: 
  == Introduction ==
  
  A common use case for Neo4j HA clusters is to direct all write requests to the master instance while using slaves for read operations.
  This allows for maximum write performance, while distributing the read load.
  This way you get read scalability and failover for your deployment.
  The most common way to achieve this is to place a load balancer in front of the HA cluster, an example being shown with <<ha-haproxy, HA Proxy>>.
  As you can see in that guide, it makes use of a REST endpoint to discover which instance is the master and direct write load to it.
  In this section, we'll deal with this REST endpoint and explain its semantics.
  
negative.code: * +/db/manage/server/ha/master+
  * +/db/manage/server/ha/slave+
  
  To use them, perform an HTTP GET operation on either and the following will be returned:
  
  .HA REST endpoint responses
  [options="header", cols="2m,<1,<2m,<2m"]
  