producer metadata behavior when topic not created

Hi, I am talking about the 0.8.2 java producer. In our deployment, we disables auto topic creation, because we would like to control the precise number of partitions created for each topic and the placement of partitions (e.g. zone-aware). I did some experimentation and checked the code. metadat

Re: Topic not created if number of live brokers less than # replicas

Hanish, Currently, we don't have plans to fix this issue in 0.8.1 since other supports such as deleting topics are probably more important. Could you work on this by pre-creating the topic when all brokers are up? Thanks, Jun On Fri, Jan 10, 2014 at 8:56 AM, Hanish Bansal < hanish.bansal.agar.

Topic not created if number of live brokers less than # replicas

Hi All, As kafka is known behavior is : number of live brokers can not be less than # replicas when creating a new topic. I raised a jira (https://issues.apache.org/jira/browse/KAFKA-1182) regarding this for improvement so that topic should be created so that in case of n replication factor we c

Re: Topic not created

Yes, could you file a jira to track that? Thanks, Jun On Thu, Dec 12, 2013 at 8:58 AM, Barto Rael wrote: > Thanks Jun for response. > > So the problem i am facing is expected behavior of kafka. > > I have just a suggestion that in case of live brokers less than # replicas: > There should be t

Re: Topic not created

Thanks Jun for response. So the problem i am facing is expected behavior of kafka. I have just a suggestion that in case of live brokers less than # replicas: There should be topic created so atleast live brokers can receive the data. They can replicate data to other broker once any down broker c

Re: Topic not created

Currently, when a topic is created, we require # live brokers to be at least # replicas. Once the topic is created, live brokers can be less than # replicas. Thanks, Jun On Thu, Dec 12, 2013 at 6:27 AM, Barto Rael wrote: > Hi All, > > We are having kafka cluster of 2 nodes. (Using Kafka 0.8.0

Topic not created

Hi All, We are having kafka cluster of 2 nodes. (Using Kafka 0.8.0 version) Replication Factor: 2 Number of partitions: 2 If any one node goes down then topic is not created in kafka. Since we are using two nodes so second node is automatically elected as leader node if down node was leader. Bel

Topic not created

Hi All, We are having kafka cluster of 2 nodes. (Using Kafka 0.8.0 version) Replication Factor: 2 Number of partitions: 2 If any one node goes down then topic is not created in kafka. Since we are using two nodes so second node is automatically elected as leader node if down node was leader. Bel