Good discussion. Stephane, we did briefly think of your options 1 and 2 but
didn’t get time to make a KIP and discuss broadly. A dynamic config is
appealing, however it has the drawback that you might end up with an
unpredictable replication factor. A minimum replication factor also needs some
ics,
hence the policy applies.
ciao,
Edo
--
Edoardo Comar
IBM Message Hub
IBM UK Ltd, Hursley Park, SO21 2JN
From: James Cheng
To: dev@kafka.apache.org
Date: 27/06/2017 09:15
Subject: Re: Minimum Replication Factor
The create.topic
in a custom create topic policy (see '
>create.topic.policy.class.name')
>--
>Edoardo Comar
>IBM Message Hub
>eco...@uk.ibm.com
>IBM UK Ltd, Hursley Park, SO21 2JN
>
>
>
>
>From: Stephane Maarek
>To: &
IBM Message Hub
eco...@uk.ibm.com
IBM UK Ltd, Hursley Park, SO21 2JN
From: Stephane Maarek
To: "dev@kafka.apache.org"
Date: 23/06/2017 01:48
Subject:Minimum Replication Factor
Hi all,
: "dev@kafka.apache.org"
Date: 23/06/2017 01:48
Subject: Minimum Replication Factor
Hi all,
Interested in getting people’s opinion on something.
The problem I have is that some people launch streams app in our cluster
but forget to set a replication factor > 1. Then it’s
Hi all,
Interested in getting people’s opinion on something.
The problem I have is that some people launch streams app in our cluster but
forget to set a replication factor > 1. Then it’s a pain to increase the
topic’s RF, when we do notice some topic partitions go offline because we
reboot
