anchor.diff:    }
   }
   ----
  +
  +. Scale up the Fluentd pods so they send new logs to Elasticsearch.
  ++
  +[source,terminal]
  +----
  +$ oc -n openshift-logging patch daemonset/logging-fluentd -p '{"spec":{"template":{"spec":{"nodeSelector":{"logging-infra-fluentd": "true"}}}}}'
  +----
  
positive.code: [id="cluster-logging-manual-rollout-rolling_{context}"]
  = Performing an Elasticsearch rolling cluster restart
  
  Perform a rolling restart when you change the `elasticsearch` config map
  or any of the `elasticsearch-*` deployment configurations.
  
  Also, a rolling restart is recommended if the nodes on which an Elasticsearch pod
  runs requires a reboot.
  
  .Prerequisites
  
  
negative.code: +
  ----
  $ oc get pods | grep elasticsearch-
  ----
  
  . Scale down the Fluentd pods so they stop sending new logs to Elasticsearch:
  +
  [source,terminal]
  ----
  $ oc -n openshift-logging patch daemonset/logging-fluentd -p '{"spec":{"template":{"spec":{"nodeSelector":{"logging-infra-fluentd": "false"}}}}}'
  ----
  
  . Perform a shard synced flush using the {product-title} link:https://github.com/openshift/origin-aggregated-logging/tree/master/elasticsearch#es_util[*es_util*] tool to ensure there are no pending operations waiting to be written to disk prior to shutting down:
  