I didn't know there's a method in the producer to get the metadata from the
broker.
I will fix my producer container.
On Wed, Sep 17, 2014 at 6:52 PM, Neha Narkhede neha.narkh...@gmail.com
wrote:
Could you make them same logic? Otherwise, I have to change implementation
of kafka producer
Also do you know what version you are running we did fix several bugs
similar to this against trunk.
-Jay
On Wed, Sep 17, 2014 at 2:14 PM, Bhavesh Mistry
mistry.p.bhav...@gmail.com wrote:
Hi Kafka Dev team,
I see my CPU spike to 100% when network connection is lost for while. It
seems
HI Jay,
I am running trunk producer based on following last commit with timestamp
Mon Sep 15 20:34:14 2014 -0700. Please let me know if this timestamp
contains the fix. Otherwise, I will file a bug with logs as Neha suggested.
commit cf0f5750b39e675cf9a9c6d6394a665366db0f58
Author: Alexis
Good to know. Does it mean release will go out after those bug is fixed or
moved to newer release? :)
Best Regards,
Mingtao
On Wed, Sep 17, 2014 at 9:34 PM, Neha Narkhede neha.narkh...@gmail.com
wrote:
You can track the list of open bugs here
Hi Mingtao,
We are shooting to cut the 0.8.2 branch this month.
Guozhang
On Thu, Sep 18, 2014 at 10:36 AM, Mingtao Zhang mail2ming...@gmail.com
wrote:
Good to know. Does it mean release will go out after those bug is fixed or
moved to newer release? :)
Best Regards,
Mingtao
On Wed, Sep
Great :)
Best Regards,
Mingtao
On Thu, Sep 18, 2014 at 2:04 PM, Guozhang Wang wangg...@gmail.com wrote:
Hi Mingtao,
We are shooting to cut the 0.8.2 branch this month.
Guozhang
On Thu, Sep 18, 2014 at 10:36 AM, Mingtao Zhang mail2ming...@gmail.com
wrote:
Good to know. Does it mean
Otis,
In kafka-1481, we will have to change the mbean names (at least the ones
with clientid and topic) anyway. Using the name/value pair in the mbean
name allows us to do this in a cleaner way. Yes, , is not allowed in
clientid or topic.
Bhavesh,
Yes, I was thinking of making changes in the
Hello all!
I'm curious about the interaction of server and topic level retention
settings. It's not clear to me the precedence of the follow:
- broker's default log.retention.bytes
- topic's retention.bytes (which defaults to broker's
log.retention.bytes)
- broker's
Hmm, yes, the fix was prior to that, that sounds like a bug.
-Jay
On Thu, Sep 18, 2014 at 9:39 AM, Bhavesh Mistry
mistry.p.bhav...@gmail.com wrote:
HI Jay,
I am running trunk producer based on following last commit with timestamp
Mon Sep 15 20:34:14 2014 -0700. Please let me know if this
Hey Jae,
The rationale for switching was to use a hash code that is cross
language and not dependent on the particular object. There are all
kinds of gotchas with Java's hashCode() as a partition assignment
strategy (e.g. two byte arrays with the same bytes will have different
hash codes).
-Jay
I am trying to understand the best practices for working with the new
(0.8.2) Producer interface.
We have a process in a large server that writes a lot of data to Kafka.
However, this data is not mission critical. When a problem arises writing
to Kafka, most specifically network issues, but also
11 matches
Mail list logo