[ https://issues.apache.org/jira/browse/KAFKA-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gwen Shapira updated KAFKA-3012: -------------------------------- Resolution: Fixed Fix Version/s: 0.9.1.0 0.9.0.1 Status: Resolved (was: Patch Available) Issue resolved by pull request 762 [https://github.com/apache/kafka/pull/762] > Avoid reserved.broker.max.id collisions on upgrade > -------------------------------------------------- > > Key: KAFKA-3012 > URL: https://issues.apache.org/jira/browse/KAFKA-3012 > Project: Kafka > Issue Type: Improvement > Affects Versions: 0.9.0.0 > Reporter: Grant Henke > Assignee: Grant Henke > Fix For: 0.9.0.1, 0.9.1.0 > > > I have seen a few issues utilizing the default value of > reserved.broker.max.id=1000 in existing clusters during upgrades. For many > that started broker.ids at 0 and incremented by 1 this may not be an issue. > However, others may have very different numbering schemes. > Given that we have the entire Integer range to work with, I propose we > increase the default to a much larger value. This will help reduce upgrade > issues and also help more clearly identify generated broker ids. > Would defaulting to 1,000,000,000 be to large? Perhaps 1,000,000 is enough. -- This message was sent by Atlassian JIRA (v6.3.4#6332)