e one that
> > > >>>>> kafka-1028 addressed.
> > > >>>>>
> > > >>>>> Here I'm trying to give a proof that current kafka doesn't
> achieve
> > > the
> > > >>>>> requireme
gt;>> messages may be chosen as the leader
> > >>>>> 2. even when replica.lag.max.messages=0, a follower can stay in ISR
> > >> when
> > >>>>> it has less messages than the leader.
> > >>>>>
> > >>>>> W
t;> We consider a cluster with 3 brokers and a topic with 3 replicas. We
> >>>>> analyze different cases according to the value of
> request.required.acks
> >>>>> (acks for short). For each case and it subcases, we find situations
> >> that
> >
>>>>> they have the same messages and are all in ISR.
>>>>>
>>>>> 1. acks=0, 1, 3. Obviously these settings do not satisfy the
>> requirement.
>>>>> 2. acks=2. Producer sends a message m. It's acknowledged by A and B. At
>>
s=M. There are two
> sub-cases:
> >>> 3.1 M>0. Suppose C be killed. C will be out of ISR after
> >>> replica.lag.time.max.ms. Then the producer publishes M messages to A
> and
> >>> B. C restarts. C will join in ISR since it is M messages behind A and
> B.
>
gt;> replica.lag.time.max.ms. Then the producer publishes M messages to A and
>>> B. C restarts. C will join in ISR since it is M messages behind A and B.
>>> Before C replicates all messages, A is killed, and C becomes leader, then
>>> message loss happens.
>>&
nd
> > C will fail out of ISR, only A keeps receiving messages. Then A is
> killed.
> > Either message loss or service blocking will happen, depending on whether
> > unclean leader election is enabled.
> >
> >
> > From: users@kafka.apache.org At: Jul 21 2014 22:28:18
om: users@kafka.apache.org At: Jul 21 2014 22:28:18
> To: JIANG WU (PRICEHISTORY) (BLOOMBERG/ 731 LEX -), users@kafka.apache.org
> Subject: Re: how to ensure strong consistency with reasonable availability
>
> You will probably need 0.8.2 which gives
> https://issues.apache.org/jira/
> > message loss happens.
> > 3.2 M=0. In this case, when the producer publishes at a high speed, B and
> > C will fail out of ISR, only A keeps receiving messages. Then A is
> killed.
> > Either message loss or service blocking will happen, depending on whethe
whether
> unclean leader election is enabled.
>
>
> From: users@kafka.apache.org At: Jul 21 2014 22:28:18
> To: JIANG WU (PRICEHISTORY) (BLOOMBERG/ 731 LEX -), users@kafka.apache.org
> Subject: Re: how to ensure strong consistency with reasonable availability
>
> You will
e.org At: Jul 21 2014 22:28:18
To: JIANG WU (PRICEHISTORY) (BLOOMBERG/ 731 LEX -), users@kafka.apache.org
Subject: Re: how to ensure strong consistency with reasonable availability
You will probably need 0.8.2 which gives
https://issues.apache.org/jira/browse/KAFKA-1028
On Mon, Jul 21, 2014 a
You will probably need 0.8.2 which gives
https://issues.apache.org/jira/browse/KAFKA-1028
On Mon, Jul 21, 2014 at 6:37 PM, Jiang Wu (Pricehistory) (BLOOMBERG/ 731
LEX -) wrote:
> Hi everyone,
>
> With a cluster of 3 brokers and a topic of 3 replicas, we want to achieve
> the following two prop
Hi everyone,
With a cluster of 3 brokers and a topic of 3 replicas, we want to achieve the
following two properties:
1. when only one broker is down, there's no message loss, and
procuders/consumers are not blocked.
2. in other more serious problems, for example, one broker is restarted twice
i
13 matches
Mail list logo
