Hello,
I have some of my own test cases very similar to the ones
in ProducerFailureHandlingTest.
I moved to the new producer against 0.8.1.1 and all of my test cases around
disconnects fail. Moving to use 0.8.2-beta on server side things succeed.
Here is an example test:
- Healthy
FYI, here is the ticket I opened for this improvement:
https://issues.apache.org/jira/browse/KAFKA-1835
Feel free to add feedback on if it meets your use case and if not how
things could.
This should make the blocking behavior explicit as long as you know all
your topics up front. Ideally a
at 11:10 PM, Paul Pearcy paul.pea...@blackboard.com
wrote:
Heya,
Playing around with the 0.8.2-beta producer client. One of my test
cases
is to ensure producers can deal with Kafka being down when the producer
is
created. My tests failed miserably because of the default blocking
On Fri, Dec 19, 2014 at 1:55 PM, Paul Pearcy ppea...@gmail.com wrote:
Hi Jay,
I have implemented a wrapper around the producer to behave like I want
it
to. Where it diverges from current 0.8.2 producer is that it accepts
three
new inputs:
- A list of expected topics
- A timeout
-ld.linkedin.biz%3E),
it seems that 0.8.2 producer should be fully compatible with 0.8.1.1
broker.
From everything I see running in a single node config, the 0.8.2 Java
producer is effectively dead after a complete disconnect to the 0.8.1.1
broker.
Thanks,
Paul
On Sun, Dec 21, 2014 at 3:06 AM, Paul Pearcy ppea
to pre-initialize the metadata to avoid blocking on the first
request you can do so by fetching the metadata using the
producer.partitionsFor(topic) api at start-up.
-Jay
On Thu, Dec 18, 2014 at 9:07 AM, Paul Pearcy ppea...@gmail.com wrote:
Hello,
Playing around with the 0.8.2-beta
.
-Jay
On Fri, Dec 19, 2014 at 9:32 AM, Paul Pearcy ppea...@gmail.com wrote:
Hi Jay,
Many thanks for the info. All that makes sense, but from an API
standpoint when something is labelled async and returns a Future, this
will
be misconstrued and developers will place async sends
Heya,
Playing around with the 0.8.2-beta producer client. One of my test cases is
to ensure producers can deal with Kafka being down when the producer is
created. My tests failed miserably because of the default blocking in the
producer with regard to metadata.fetch.timeout.ms. The first line
Hello,
Playing around with the 0.8.2-beta producer client. One of my test cases
is to ensure producers can deal with Kafka being down when the producer is
created. My tests failed miserably because of the default blocking in the
producer with regard to metadata.fetch.timeout.ms. The first line
