anchor.diff:  = Storage considerations for OpenShift Logging and {product-title}
   
   ////
  -An Elasticsearch index is a collection of primary shards and its corresponding replica
  -shards. This is how Elasticsearch implements high availability internally, so there
  -is little requirement to use hardware based mirroring RAID variants. RAID 0 can still
  -be used to increase overall disk performance.
  +An Elasticsearch index is a collection of primary shards and their corresponding replica shards. This is how Elasticsearch implements high availability internally, so there is little requirement to use hardware based mirroring RAID variants. RAID 0 can still be used to increase overall disk performance.
   ////
   
  -A persistent volume is required for each Elasticsearch deployment configuration. On {product-title} this is achieved using
  -persistent volume claims.
  +A persistent volume is required for each Elasticsearch deployment configuration. On {product-title} this is achieved using persistent volume claims.
   
   The Elasticsearch Operator names the PVCs using the Elasticsearch resource name.
   
  
positive.code: 
  Fluentd ships any logs from *systemd journal* and **/var/log/containers/*.log** to Elasticsearch.
  
  Therefore, consider how much data you need in advance and that you are
  aggregating application log data. Some Elasticsearch users have found that it
  is necessary to keep absolute storage consumption around 50% and below 70% at all times. This
  helps to avoid Elasticsearch becoming unresponsive during large merge
  operations.
  
  By default, at 85% Elasticsearch stops allocating new data to the node, at 90% Elasticsearch attempts to relocate
  existing shards from that node to other nodes if possible. But if no nodes have free capacity below 85%, Elasticsearch effectively rejects creating new indices
  and becomes RED.
  
  [NOTE]
  ====
  These low and high watermark values are Elasticsearch defaults in the current release. You can modify these values,
  but you also must apply any modifications to the alerts also. The alerts are based
  on these defaults.
  ====
  
negative.code: |===
  
  
  Calculating the total logging throughput and disk space required for your {product-title} cluster requires knowledge of your applications. For example, if one of your applications on average logs 10 lines-per-second, each 256 bytes-per-line, calculate per-application throughput and disk space as follows:
  
  ----
   (bytes-per-line * (lines-per-second) = 2560 bytes per app per second
  