[
https://issues.apache.org/jira/browse/KAFKA-3012?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15095543#comment-15095543
]
Grant Henke commented on KAFKA-3012:
------------------------------------
Through discussion
[here|http://search-hadoop.com/m/uyzND1LHQWW23C0j&subj=Consider+increasing+the+default+reserved+broker+max+id]
it has been shown that a compatible and universal change that prevents all
collisions would be difficult. The patch provided instead provides users who
are manually configuring their broker ids to opt out of auto generation all
together. This option will also prevent an accidental uses of the auto
generation feature in environments where its use is unfavorable.
I would have liked to default it to false and make the user opt into auto
generation. However, thats not a compatible change given that it is already
enabled by default in 0.9.0.
> 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
>
> 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)
