|
@@ -77,7 +77,7 @@ This problem is mostly fixed by {GIT}20384[#20384] (v5.0.0), which takes committ
|
|
|
election. This considerably reduces the chance of this rare problem occurring but does not fully mitigate it. If the second partition
|
|
election. This considerably reduces the chance of this rare problem occurring but does not fully mitigate it. If the second partition
|
|
|
happens concurrently with a cluster state update and blocks the cluster state commit message from reaching a majority of nodes, it may be
|
|
happens concurrently with a cluster state update and blocks the cluster state commit message from reaching a majority of nodes, it may be
|
|
|
that the in flight update will be lost. If the now-isolated master can still acknowledge the cluster state update to the client this
|
|
that the in flight update will be lost. If the now-isolated master can still acknowledge the cluster state update to the client this
|
|
|
-will amount to the loss of an acknowledged change. Fixing that last scenario needs considerable work and is currently targeted at (v6.0.0).
|
|
|
|
|
|
|
+will amount to the loss of an acknowledged change. Fixing that last scenario needs considerable work. We are currently working on it but have no ETA yet.
|
|
|
|
|
|
|
|
[float]
|
|
[float]
|
|
|
=== Better request retry mechanism when nodes are disconnected (STATUS: ONGOING)
|
|
=== Better request retry mechanism when nodes are disconnected (STATUS: ONGOING)
|
Boaz Leskes