You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Jay Kreps (JIRA)" <ji...@apache.org> on 2015/12/07 19:01:10 UTC
[jira] [Created] (KAFKA-2956) Upgrade section of the docs is still
a bit anemic
Jay Kreps created KAFKA-2956:
--------------------------------
Summary: Upgrade section of the docs is still a bit anemic
Key: KAFKA-2956
URL: https://issues.apache.org/jira/browse/KAFKA-2956
Project: Kafka
Issue Type: Improvement
Affects Versions: 0.9.0.0
Reporter: Jay Kreps
Upgrades are pretty touchy since one wrong move can really mess up your cluster. We want to give people all the info about how to do this safely so that they do do it (we've historically had people lagging on version for a very long time, mostly out of fear).
Here is some of the obvious missing stuff:
1. Break out the two cases of "rolling upgrade" vs "downtime upgrade" most people will be doing both. We have both but they should each have their own section.
2. What about clients? Do they need to go first? Second? What about non-java clients?
3. What about mirroring? Can old clusters mirror to new clusters? Can new clusters mirror to old clusters? Do the servers need to upgrade first or the mirror makers?
Basically it would be good to really walk people through this step by step so that they get in the habit of doing it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)