From 96feb479cde5cf9cc578e5182146472d2e3edc3a Mon Sep 17 00:00:00 2001 From: Caroline1000 Date: Fri, 8 Jun 2018 15:25:26 -0700 Subject: [PATCH] add order change needed for KIS in 0.12.0 (#5760) --- docs/content/operations/rolling-updates.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/content/operations/rolling-updates.md b/docs/content/operations/rolling-updates.md index 4ebcfd97086..1139cc5461e 100644 --- a/docs/content/operations/rolling-updates.md +++ b/docs/content/operations/rolling-updates.md @@ -9,12 +9,14 @@ For rolling Druid cluster updates with no downtime, we recommend updating Druid following order: 1. Historical -2. Overlord (if any) -3. Middle Manager (if any) +2. \*Overlord (if any) +3. \*Middle Manager (if any) 4. Standalone Real-time (if any) 5. Broker 6. Coordinator ( or merged Coordinator+Overlord ) +\* In 0.12.0, there are protocol changes between the Kafka supervisor and Kafka Indexing task and also some changes to the metadata formats persisted on disk. Therefore, to support rolling upgrade, all the Middle Managers will need to be upgraded first before the Overlord. Note that this ordering is different from the standard order of upgrade, also note that this ordering is only necessary when using the Kafka Indexing Service. If one is not using Kafka Indexing Service or can handle down time for Kafka Supervisor then one can upgrade in any order. + ## Historical Historical nodes can be updated one at a time. Each Historical node has a startup time to memory map