From b8f6a93fabd62b9df2c516153993773cadadc04f Mon Sep 17 00:00:00 2001
From: clemcnt <clement.contet@protonmail.com>
Date: Thu, 12 Jan 2023 13:23:37 +0100
Subject: [PATCH] Commentaires cluster change + slide 19

---
 slides.md | 18 ++++++++++++++++++
 1 file changed, 18 insertions(+)

diff --git a/slides.md b/slides.md
index 4846544..bc0b24d 100644
--- a/slides.md
+++ b/slides.md
@@ -395,6 +395,16 @@ AppendEntries RPCs include <index, term> of entry preceding new one(s)
 
 ![bg 80%](figs/cluster-change.png)
 
+<!--
+
+- Dashed lines show configuration entries that have been created but not committed, 
+- solid lines show the latest committed configuration entry. 
+- The leader first creates the Cold,new configuration entry in its log and commits it to Cold,new (a majority of Cold and a majority of Cnew). 
+- Then it creates the Cnew entry and commits it to a majority of Cnew. 
+- There is no point in time in which Cold and Cnew can both make decisions independently.
+
+-->
+
 <!-- Clément -->
 
 ---
@@ -427,6 +437,14 @@ AppendEntries RPCs include <index, term> of entry preceding new one(s)
 
 ![bg 90%](https://ongardie.net/static/coreosfest/slides/timeoutcdf.svg)
 
+
+<!-- 
+
+- a small amount of randomization in the election timeout is enough to avoid split votes in elections. 
+- In the absence of randomness, leader election consistently took longer than 10 seconds in our tests due to many split votes. Adding just 5ms of randomness helps significantly, resulting in a median downtime of 287ms. 
+- Using more randomness improves worst-case behavior: with 50ms of randomness the worstcase completion time (over 1000 trials) was 513ms.
+
+-->
 <!-- Clément -->
 
 ---