anchor.diff:  }
   ----
   
  -TIP: It is recommended that the value of `waitFor` configuration for node lost trigger be larger than a minute so that large full garbage collection pauses do not cause this trigger to generate events and needlessly move or delete replicas in the cluster.
  -
  -== Auto Add Replicas Trigger
  +TIP: It is recommended that the value of `waitFor` configuration for the node lost trigger be larger than 1 minute so that large full garbage collection pauses do not cause this trigger to generate events and needlessly move or delete replicas in the cluster.
  +
  +=== Auto Add Replicas Trigger
   
   When a collection has the parameter `autoAddReplicas` set to true then a trigger configuration named `.auto_add_replicas` is automatically created to watch for nodes going away. This trigger produces `nodeLost` events,
   which are then processed by configured actions (usually resulting in computing and executing a plan
  
positive.code: }
  ----
  
  == Node Lost Trigger
  
  The `NodeLostTrigger` generates `nodeLost` events when a node leaves the cluster. It can be used to either move replicas
  that were hosted by the lost node to other nodes or to delete them from the cluster.
  
  Apart from the parameters described at <<#trigger-configuration, Trigger Configuration>>, this trigger supports the following configuration:
  
  `preferredOperation`:: (string, optional, defaults to `MOVEREPLICA`) The operation to be performed in response to an event generated by this trigger. By default, replicas will be moved from the lost nodes to the other nodes in the cluster. The only other supported value is `DELETENODE` which deletes all information about replicas that were hosted by the lost node.
  
  
negative.code: }
  ----
  
  === Index Size Trigger
  This trigger can be used for monitoring the size of collection shards, measured either by the
  number of documents in a shard or the physical size of the shard's index in bytes.
  
  