[ https://issues.apache.org/jira/browse/KAFKA-1864?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14279616#comment-14279616 ]
Jun Rao commented on KAFKA-1864: -------------------------------- Attached is a patch. A couple of the unit tests fail because of KAFKA-1867. Fixing KAFKA-1867 is a bit tricky and we probably don't want to do that in 0.8.2. So, patching the unit test by overriding the default value for offsets.topic.replication.factor for now. > 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)
