Hi Kriti,
You will have to implement the Principal Builder interface and provide the full
class path in broker config. I don't remember the exact config name right now,
but you can search for some config by name "principalbuilder.class" in the
broker configs.
Once you do this, Kafka will auto
If you are using the new producer, the send api returns a future on which you
can do a .get() to be sure that the message has made it to Kafka and than do
another send. I am not sure if the .Net producer that you are referring to
exposes this functionality.
Thanks,
Mayuresh
Sent from my iPho
You can configure that in the Configs by setting log retention :
http://kafka.apache.org/07/configuration.html
Thanks,
Mayuresh
Sent from my iPhone
> On Jul 24, 2015, at 12:49 PM, Yuheng Du wrote:
>
> Hi,
>
> I am testing the kafka producer performance. So I created a queue and
> writes a l
This is not unclean leader election since the follower is still in ISR. Yes we
will loose those 2000 messages.
Mayuresh
Sent from my iPhone
> On May 20, 2015, at 8:31 AM, tao xiao wrote:
>
> Hi team,
>
> I know that if a broker is behind the leader by no more than
> replica.lag.max.messages
Try bouncing
10.144.38.185
This should resolve the issue.
Thanks,
Mayuresh
Sent from my iPhone
> On Apr 20, 2015, at 8:22 PM, 小宇 wrote:
>
> 10.144.38.185
I am not sure if that's how it works.
I suppose each consumer should be able to consume from all the topics right. If
not then it looks weird.
Thanks,
Mayuresh
Sent from my iPhone
> On Mar 20, 2015, at 7:15 PM, Jiangjie Qin wrote:
>
> Hi Jason,
>
> The motivation behind round robin is to
Is your topic log compacted? Also if it is are the messages keyed? Or are the
messages compressed?
Thanks,
Mayuresh
Sent from my iPhone
> On Mar 14, 2015, at 2:02 PM, Zakee wrote:
>
> Thanks, Jiangjie for helping resolve the kafka controller migration driven
> partition leader rebalance iss
In that case you will have to maintain the offsets consumed and reset the
offsets in case you need to consume from past.
For example, suppose you have a userA for which you have a partitionA for topic
TopicA. Each page shown to user increments the offset by 10. You have consumed
till offset 100
Yes. That's correct.
Thanks,
Mayuresh
Sent from my iPhone
> On Jan 8, 2015, at 2:55 PM, Xiaoyu Wang wrote:
>
> Hi All,
>
> Just want to double check with you regarding producers using required.acks
> = -1.
>
> - Producer is guaranteed to receive responses within certain time.
> Because