Add talk about healthcheck and multi-site by Tony and Luca Change-Id: I35e8b29e6f441fd07a11994eb3807bcb1abec109
diff --git a/schedule.md b/schedule.md index 7362915..42e4fe2 100644 --- a/schedule.md +++ b/schedule.md
@@ -58,7 +58,7 @@ | 14:45 | [Gerrit adoption and NoteDb migration user story](sessions/gerrit-user-story.md) | 15:30 | Break & Networking | 16:00 | [Using Gerrit with Zuul](sessions/gerrit-and-zuul.md) -| 16:45 | __Talk available__ +| 16:45 | [How healthcheck and multi-site saves keep your sleep at night](sessions/healthcheck-multi-site-keep-sleep-at-night.md)) | 17:30 | Party and free drinks ### Friday, 11th of November
diff --git a/sessions/healthcheck-multi-site-keep-sleep-at-night.md b/sessions/healthcheck-multi-site-keep-sleep-at-night.md new file mode 100644 index 0000000..614c52a --- /dev/null +++ b/sessions/healthcheck-multi-site-keep-sleep-at-night.md
@@ -0,0 +1,22 @@ +# How the healthcheck plugin and multi-site keep your sleep at night + +GerritHub.io had an outage on the 3rd of November at 15:20 GMT, which +was caused by a [critical Gerrit issue](https://bugs.chromium.org/p/gerrit/issues/detail?id=16384) +discovered that day. + +The issue was deep into the core of Gerrit, involving loading the +accounts external-ids, impacting pretty much anything that required +authenticated traffic. However, none of the GerritHub.io users +noticed any issues, delays, slow down, or reduced functionality. + +In this talk, Tony and Luca will describe what happened and how +the GerritForge Team detected, analyzed, and mitigated the problem, +avoiding a global outage. + +The learnings from this story can help other Gerrit admins to +set up operating practices about metrics, high availability, +and service resilience with Gerrit that can be useful in +preventing sleepless nights and managing outages. + +*[Luca Milanesio, GerritForge](../speakers.md#lmilanesio)* +*[Antonio Barone, GerritForge](../speakers.md#abarone)*