You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@kafka.apache.org by "Gwen Shapira (JIRA)" <ji...@apache.org> on 2015/01/08 04:50:34 UTC

[jira] [Commented] (KAFKA-1846) Offset storage topic should not default to replication factor 1

    [ https://issues.apache.org/jira/browse/KAFKA-1846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14268790#comment-14268790 ] 

Gwen Shapira commented on KAFKA-1846:
-------------------------------------

Being able to set the default replication factor to -1 with same semantics will be very helpful too.

For same reasons - better out-of-the-box experience combined with extra safety for those who rely on automated topic creation.

> Offset storage topic should not default to replication factor 1
> ---------------------------------------------------------------
>
>                 Key: KAFKA-1846
>                 URL: https://issues.apache.org/jira/browse/KAFKA-1846
>             Project: Kafka
>          Issue Type: Improvement
>    Affects Versions: 0.8.2
>            Reporter: Jay Kreps
>              Labels: newbie
>             Fix For: 0.8.3
>
>
> Currently the offset storage topic defaults to replication factor 1 (offsets.topic.replication.factor). Presumably this is because we want to make the single-node case work well "out of the box". But this is one of those obscure settings most people won't really know about so most people won't realize they are running this without replication. It would be better to change the default in KafkaConfig to -1 and have this set the replication factor dynamically when that topic is created to be the min(3,total_nodes), if on the other hand the user sets some value here we would use that.
> In the absence of this I think many people will not realize what is happening until suddenly a broker dies and they can't commit offsets.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)