GitHub user edenhill opened a pull request:
https://github.com/apache/kafka/pull/670
Documentation updates for reserved.broker.max.id
People are facing problems upgrading their clusters with configured broker
IDs above 1000 due to `reserved.broker.max.id` which wasn't very well announced.
This PR attempts to improve that somewhat by fixing the broker config docs
and adding a note to the upgrade documentation.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/edenhill/kafka docs-reserved.broker.max.id
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/kafka/pull/670.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 #670
----
commit 062ee390c130042247fcfe5d8f05b61c698a1342
Author: Magnus Edenhill <mag...@edenhill.se>
Date: 2015-12-11T18:44:07Z
Upgrade docs: added note on reserved.broker.max.id
commit de1307ea2403d0e72f998e556e26c032d43a807a
Author: Magnus Edenhill <mag...@edenhill.se>
Date: 2015-12-11T18:44:22Z
Docs: fixed description of reserved.broker.max.id
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
