This is on 0.8.
Zayeem
On Thu, Feb 28, 2013 at 10:44 PM, Neha Narkhede wrote:
> Do you see this error on Kafka 0.7.2 or 0.8 ? I think this error message is
> very unclear, filed https://issues.apache.org/jira/browse/KAFKA-778 to fix
> it.
>
> Thanks,
> Neha
>
>
> On Thu, Feb 28, 2013 at 4:53 PM
Do you see this error on Kafka 0.7.2 or 0.8 ? I think this error message is
very unclear, filed https://issues.apache.org/jira/browse/KAFKA-778 to fix
it.
Thanks,
Neha
On Thu, Feb 28, 2013 at 4:53 PM, zayeem wrote:
> When trying to create a topic and sending a test payload results in the
> fol
Hello,
I actually tried to load the data back with the same instance of kafka
on server A so the broker id must be the same. The reason I brought
this up at the first place is because we've had some issues
recognizing the messages on a server stop/restart. I was able to
reproduce our issue with fo
Right, everything has to go through the leader. If the producer waits for
ack=committed, it will get an exception when sending m3. So the producer is
aware of that m3 may not be committed by the broker. The producer can
choose to resend m3 if it wants to be sure that m3 is safely stored at the
brok
Excellent thanks!
BTW, in the slides, it shows the the message 'm3' is lost.
I guess the leader is the single point of failure then when a producer
sends a message, meaning it can never bypass the leader and write to the
followers in case of leader failure right?
On Thu, Feb 28, 2013 at 8:35 AM
I'm guessing the brokerid of the new broker is not the same as the old one
maybe ? This will work only if you copy the data over and maintain the same
broker id.
If not, then this could be a bug.
Thanks,
Neha
On Thu, Feb 28, 2013 at 3:21 AM, Jason Huang wrote:
> I've started by only coping $l
Thanks Jun, great slides!
On Wed, Feb 27, 2013 at 11:52 PM, Jun Rao wrote:
> Hi,
>
> I gave a talk on Kafka replication at ApacheCon yesterday. The slides can
> be found at
> http://www.slideshare.net/junrao/kafka-replication-apachecon2013(it's
> also added to Kafka wiki). I will share the link
I've started by only coping $log.dir from server A to server B. Both
server A and server B ran same version of kafka 0.8 with same
configuration files.
However, after running kafka 0.8 on server B I get the following
exception when I tried to fetch the message:
2013-02-28 05:56:35,851] WARN [Kafka
