Hey guys
Seeing the following set of errors when sending messages to the client via
the API. Thing is 4 out of 5 messages get in, and only one message is being
lost, and I haven’t been able to pinpoint the culprit. Listed below are the
only set of errors I see on my kafka out logs. Any advice is g
Hey Jun
Its kafka-2.9.2-0.8.1.5
Great presentations kafka on youtube btw!
-Kart
I have noticed some strange patterns when testing with the 0.8.1 build and
the 0.8.2 builds, and are listed below.
1. So I setup a brand new cluster [3 kafka nodes with 3 zookeepers],
created 2 topics via the API calls, everything went fine and was
successfully able to view my messages in my consum
, Feb 19, 2015 at 11:39 AM, Jun Rao wrote:
> Zookeeper requires a majority of the nodes to be up for the service to be
> available. Kafka relies on Zookeeper to be always available.
>
> Thanks,
>
> Jun
>
> On Thu, Feb 19, 2015 at 11:15 AM, Karts wrote:
>
> > I h
yes i did.
On Thu, Feb 19, 2015 at 2:42 PM, Jun Rao wrote:
> Did you consume the messages from the beginning of the log?
>
> Thanks,
>
> Jun
>
> On Thu, Feb 19, 2015 at 12:18 PM, Karts wrote:
>
> > but they have always been up. I mean when i was testing, all the
actually i take that back. it reads from where the last offset left off.
On Thu, Feb 19, 2015 at 4:20 PM, Karts wrote:
> yes i did.
>
> On Thu, Feb 19, 2015 at 2:42 PM, Jun Rao wrote:
>
>> Did you consume the messages from the beginning of the log?
>>
>> Thanks,
of things.
On Thu, Feb 19, 2015 at 4:30 PM, Jun Rao wrote:
> Is there any error in the producer log? Is there any pattern in the
> messages being lost?
>
> Thanks,
>
> Jun
>
> On Thu, Feb 19, 2015 at 4:20 PM, Karts wrote:
>
> > yes i did.
> >
> > On Thu
unsubscribe
On Wed, Aug 21, 2019 at 2:23 AM sampath kumar wrote:
> Hi,
>
> Using Broker 5.3.0, new consumers(Consumers managed by brokers). Brokers
> are deployed in a Kubernetes environment
>
> Number of brokers : 3, Number of 3 Zookeeper setup
>
> One of the Topic "inventory.request" we have 3
