You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Grant Henke (JIRA)" <ji...@apache.org> on 2015/07/16 16:33:04 UTC
[jira] [Commented] (KAFKA-2336) Changing
offsets.topic.num.partitions after the offset topic is created breaks
consumer group partition assignment
[ https://issues.apache.org/jira/browse/KAFKA-2336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14629815#comment-14629815 ]
Grant Henke commented on KAFKA-2336:
------------------------------------
Created reviewboard https://reviews.apache.org/r/36548/diff/
against branch origin/trunk
> Changing offsets.topic.num.partitions after the offset topic is created breaks consumer group partition assignment
> -------------------------------------------------------------------------------------------------------------------
>
> Key: KAFKA-2336
> URL: https://issues.apache.org/jira/browse/KAFKA-2336
> Project: Kafka
> Issue Type: Bug
> Components: core
> Affects Versions: 0.8.2.1
> Reporter: Grant Henke
> Assignee: Grant Henke
> Attachments: KAFKA-2336.patch
>
>
> Currently adjusting offsets.topic.num.partitions after the offset topic is created is not supported. Meaning that the number of partitions will not change once the topic has been created.
> However, changing the value in the configuration should not cause issues and instead simply be ignored. Currently this is not the case.
> When the value of offsets.topic.num.partitions is changed after the offset topic is created the consumer group partition assignment completely changes even though the number of partitions does not change.
> This is because _kafka.server.OffsetManager.partitionFor(group: String)_ uses the configured value and not the value of the actual topic.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)