[ https://issues.apache.org/jira/browse/KAFKA-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15124312#comment-15124312 ]
ASF GitHub Bot commented on KAFKA-3164: --------------------------------------- GitHub user granthenke opened a pull request: https://github.com/apache/kafka/pull/838 KAFKA-3164: Document client and mirrormaker upgrade procedure/require… …ments You can merge this pull request into a Git repository by running: $ git pull https://github.com/granthenke/kafka upgrade-docs Alternatively you can review and apply these changes as the patch at: https://github.com/apache/kafka/pull/838.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #838 ---- commit e855bfb711348b0fd880d7f4fc2c54cd31e80ef8 Author: Grant Henke <granthe...@gmail.com> Date: 2016-01-29T22:09:04Z KAFKA-3164: Document client and mirrormaker upgrade procedure/requirements ---- > Document client and mirrormaker upgrade procedure/requirements > -------------------------------------------------------------- > > Key: KAFKA-3164 > URL: https://issues.apache.org/jira/browse/KAFKA-3164 > Project: Kafka > Issue Type: Improvement > Affects Versions: 0.9.0.0 > Reporter: Grant Henke > Assignee: Grant Henke > Priority: Minor > > Many users in the mailing list have asked questions about new clients working > on old brokers, and mirrormaker breaking when upgrading to 0.9.0. Adding a > section to the upgrade docs to let users know to upgrade brokers before > clients and downstream mirrormaker first should help other users from making > the same mistake. -- This message was sent by Atlassian JIRA (v6.3.4#6332)