[
https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279677#comment-14279677
]
Jun Rao commented on KAFKA-1864:
--------------------------------
Also, another impact in this patch is that the offset topic may not be
guaranteed to be created with the configured offset replication factor since we
take the min btw the configured value and the # of live brokers. An alternative
is to use negative values as suggested in KAFKA-1846 as the default. Then we
can treat the positive values as the hard requirement. Not sure if this will
cause more confusing.
> Revisit defaults for the internal offsets topic
> -----------------------------------------------
>
> Key: KAFKA-1864
> URL: https://issues.apache.org/jira/browse/KAFKA-1864
> Project: Kafka
> Issue Type: Bug
> Affects Versions: 0.8.2
> Reporter: Neha Narkhede
> Assignee: Jun Rao
> Priority: Blocker
> Attachments: kafka-1864.patch
>
>
> Realize this is late, but as I was reviewing the 0.8.2 RC, I found that our
> defaults for the offsets topic are not ideal. The # of partitions currently
> default to 1 and the replication factor is 1 as well. Granted that the
> replication factor is changeable in the future (through the admin tool),
> changing the # of partitions is a very disruptive change. The concern is that
> this feature is on by default on the server and will be activated the moment
> the first client turns on kafka based offset storage.
> My proposal is to change the # of partitions to something large (50 or so)
> and change the replication factor to min(# of alive brokers, configured
> replication factor)
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
