Apache
/
druid
mirror of https://github.com/apache/druid.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

add order change needed for KIS in 0.12.0 (#5760)

This commit is contained in:
Caroline1000 2018-06-08 15:25:26 -07:00 committed by Jihoon Son
parent b7e8812d18
commit 96feb479cd
1 changed files with 4 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
docs/content/operations/rolling-updates.md
View File

@ -9,12 +9,14 @@ For rolling Druid cluster updates with no downtime, we recommend updating Druid
following order: following order:
1. Historical 1. Historical
2. Overlord (if any) 2. \*Overlord (if any)
3. Middle Manager (if any) 3. \*Middle Manager (if any)
4. Standalone Real-time (if any) 4. Standalone Real-time (if any)
5. Broker 5. Broker
6. Coordinator ( or merged Coordinator+Overlord ) 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
Historical nodes can be updated one at a time. Each Historical node has a startup time to memory map Historical nodes can be updated one at a time. Each Historical node has a startup time to memory map