anchor.diff:  . Configure ZooKeeper
   +
   In reality, you should carefully consider your ZooKeeper configuration.
  -You can find out more about configuring ZooKeeper in <<zookeeper,zookeeper>>.
  +You can find out more about configuring ZooKeeper in <<zookeeper,zookeeper>> section.
   This configuration will direct HBase to start and manage a ZooKeeper instance on each node of the cluster.
   +
   On `node-a`, edit _conf/hbase-site.xml_ and add the following properties.
  
positive.code: 
  . Test password-less login.
  +
  If you performed the procedure correctly, if you SSH from `node-a` to either of the other nodes, using the same username, you should not be prompted for a password.
  
  . Since `node-b` will run a backup Master, repeat the procedure above, substituting `node-b` everywhere you see `node-a`.
    Be sure not to overwrite your existing _.ssh/authorized_keys_ files, but concatenate the new key onto the existing file using the `>>` operator rather than the `>` operator.
  
  .Procedure: Prepare `node-a`
  
  `node-a` will run your primary master and ZooKeeper processes, but no RegionServers.
  . Stop the RegionServer from starting on `node-a`.
  
  . Edit _conf/regionservers_ and remove the line which contains `localhost`. Add lines with the hostnames or IP addresses for `node-b` and `node-c`.
  +
  
negative.code: [NOTE]
  ====
  The `HQuorumPeer` process is a ZooKeeper instance which is controlled and started by HBase.
  If you use ZooKeeper this way, it is limited to one instance per cluster node and is appropriate for testing only.
  If ZooKeeper is run outside of HBase, the process is called `QuorumPeer`.
  For more about ZooKeeper configuration, including using an external ZooKeeper instance with HBase, see <<zookeeper,zookeeper>> section.
  ====
  
  . Browse to the Web UI.
  