anchor.diff:  |===
   
   The node quorum and recovery settings in the template were set based on the
  -`*es-[ops-]cluster-size*` value initially provided to the deployer. Since the
  +`es-[ops-]cluster-size` value initially provided to the deployer. Since the
   cluster size is changing, those values need to be overridden.
   
   . The existing deployment configurations for that cluster also need to have the
  
positive.code: here) is _not_ aggregated into *.operations* and is found under its ID.
  ====
  
  If you set `*enable-ops-cluster*` to *true* for the deployer, Fluentd is
  configured to split logs between the main ElasticSearch cluster and another
  cluster reserved for operations logs (which are defined as node system logs and
  the projects *default*, *openshift*, and *openshift-infra*). Therefore, a
  
negative.code: By far the simplest way to change the scale of Elasticsearch is to
  reinstall the whole deployment. Assuming you have supplied persistent
  storage for the deployment, this should not be very disruptive. Simply
  re-run the deployer with the updated `es-cluster-size` configuration
  value and the `MODE=reinstall` template parameter. For example:
  
  ----
  $ oc edit configmap logging-deployer
  