Hi all,
We're experiencing high cpu usage on some of our development machines when
kafka should be idle. These are single node kafka instances used only for
development, so far we haven't seen any problems on our production system.
It doesn't seem to happen until we deploy a storm topology and
? I'm also going to ask on the storm list
about this setting.
Cheers,
Craig
On Thu, Jul 16, 2015 at 8:41 AM, Craig Ching craigch...@gmail.com wrote:
Hi all,
We're experiencing high cpu usage on some of our development machines when
kafka should be idle. These are single node kafka instances
r debug logs here:
> kafka/config/tools-log4j.properties
>
> On Wed, Jun 13, 2018 at 9:55 AM Craig Ching wrote:
>
>> Hi!
>>
>> We’re having a problem with a new kafka cluster at 1.1.0. The problem is,
>> in general, that consumers can’t consume from the
This didn’t fix my problem unfortunately. Both time stamps are 0.
> On Jul 24, 2018, at 15:22, Craig Ching wrote:
>
> Hey, thanks for that Dmitriy! I'll have a look.
>
>> On Tue, Jul 24, 2018 at 11:18 AM Dmitriy Vsekhvalnov
>> wrote:
>> Not really associate
mestamp)
fmt.Println("Received messages", string(msg.Key), string(msg.Value))
case <-signals:
fmt.Println("Interrupt is detected")
break
}
}
}()
<-signals
}
On Mon, Jul 23, 2018 at 10:43 AM Dmitriy Vsekhvalnov
wrote:
> Hey Craig,
>
> what exact problem you have
gt;
> Try using msg.BlockTimestamp instead of msg.Timestamp and see if it helps.
>
> On Tue, Jul 24, 2018 at 3:26 AM Craig Ching wrote:
>
> > Hi Dmitry,
> >
> > Are you associated with the Sarama project? If so, understand that part
> of
> > what I want
Hi Craig Ching,
>
> Reg. *We did end up turning on debug logs for the console consumer and
> found that one broker seemed to be having problems, it would lead to
> timeouts communicating with it. After restarting that broker, things
> sorted themselves out.*
>
> We had similar
Hi!
I'm working on debugging a problem with how message timestamps are handled
in the sarama client. In some cases, the sarama client won't associate a
timestamp with a message while the kafka console consumer does. I've found
the documentation on the message format here:
