anchor.diff:  See {GIT}9967[#9967]. (STATUS: ONGOING)
   
   [float]
  -=== Wait on incoming joins before electing local node as master (STATUS: ONGOING)
  +=== OOM resiliency (STATUS: ONGOING)
  +
  +The family of circuit breakers has greatly reduced the occurrence of OOM
  +exceptions, but it is still possible to cause a node to run out of heap
  +space.  The following issues have been identified:
  +
  +* Set a hard limit on `from`/`size` parameters {GIT}9311[#9311]. (STATUS: ONGOING)
  +* Prevent combinatorial explosion in aggregations from causing OOM {GIT}8081[#8081]. (STATUS: ONGOING)
  +* Add the byte size of each hit to the request circuit breaker {GIT}9310[#9310]. (STATUS: ONGOING)
  +
  +[float]
  +=== Loss of documents during network partition (STATUS: ONGOING)
  +
  +If a network partition separates a node from the master, there is some window of time before the node detects it. The length of the window is dependent on the type of the partition. This window is extremely small if a socket is broken. More adversarial partitions, for example, silently dropping requests without breaking the socket can take longer (up to 3x30s using current defaults).
  +
  +If the node hosts a primary shard at the moment of partition, and ends up being isolated from the cluster (which could have resulted in {GIT}2488[split-brain] before), some documents that are being indexed into the primary may be lost if they fail to reach one of the allocated replicas (due to the partition) and that replica is later promoted to primary by the master. {GIT}7572[#7572]
  +
  +A test to replicate this condition was added in {GIT}7493[#7493].
  +
  +[float]
  +=== Jepsen Test Failures (STATUS: ONGOING)
  +
  +We have increased our test coverage to include scenarios tested by Jepsen. We make heavy use of randomization to expand on the scenarios that can be tested and to introduce new error conditions. You can follow the work on the master branch of the https://github.com/elastic/elasticsearch/blob/master/core/src/test/java/org/elasticsearch/discovery/DiscoveryWithServiceDisruptionsIT.java[`DiscoveryWithServiceDisruptionsIT` class], where we will add more tests as time progresses.
  +
  +[float]
  +=== Document guarantees and handling of failure (STATUS: ONGOING)
  +
  +This status page is a start, but we can do a better job of explicitly documenting the processes at work in Elasticsearch, and what happens in the case of each type of failure. The plan is to have a test case that validates each behavior under simulated conditions. Every test will document the expected results, the associated test code and an explicit PASS or FAIL status for each simulated case.
  +
  +[float]
  +=== Do not allow stale shards to automatically be promoted to primary (STATUS: ONGOING)
  +
  +In some scenarios, after loss of all valid copies, a stale replica shard can be assigned as a primary. This can lead to
  +a loss of acknowledged writes if the valid copies are not lost but are rather temporarily isolated. Work is underway
  +({GIT}14671[#14671]) to prevent the automatic promotion of a stale primary and only allow such promotion to occur when
  +a system operator manually intervenes.
  +
  +== Completed
  +
  +[float]
  +=== Wait on incoming joins before electing local node as master (STATUS: DONE, v2.0.0)
   
   During master election each node pings in order to discover other nodes and validate the liveness of existing
   nodes. Based on this information the node either discovers an existing master or, if enough nodes are found
  
positive.code: We are committed to tracking down and fixing all the issues that are posted.
  
  [float]
  === Use two phase commit for Cluster State publishing (STATUS: ONGOING)
  
  A master node in Elasticsearch continuously https://www.elastic.co/guide/en/elasticsearch/reference/current/modules-discovery-zen.html#fault-detection[monitors the cluster nodes]
  and removes any node from the cluster that doesn't respond to its pings in a timely
  
negative.code: nodes have sent their joins request (based on the `minimum_master_nodes` settings) the cluster state is updated.
  {GIT}12161[#12161]
  
  [float]
  === Mapping changes should be applied synchronously (STATUS: DONE, v2.0.0)
  
  When introducing new fields using dynamic mapping, it is possible that the same
  field can be added to different shards with different data types.  Each shard
  