even the Cluster is
> available.
>
> Thanks
> Ankit Jain
>
>> On Wed, Jun 7, 2017 at 12:56 PM, Hans Jespersen wrote:
>>
>> Try adding props.put("max.block.ms", "0");
>>
>> -hans
>>
>>
>>
>>> On Jun 7, 2017, at
Jun 7, 2017, at 12:24 PM, Ankit Jain wrote:
> >
> > Hi,
> >
> > We want to use the non blocking Kafka producer. The producer thread
> should
> > not block if the Kafka is cluster is down or not reachable.
> >
> > Currently, we are setting following properties bu
Try adding props.put("max.block.ms", "0");
-hans
> On Jun 7, 2017, at 12:24 PM, Ankit Jain wrote:
>
> Hi,
>
> We want to use the non blocking Kafka producer. The producer thread should
> not block if the Kafka is cluster is down or not reachable.
&g
Hi,
We want to use the non blocking Kafka producer. The producer thread should
not block if the Kafka is cluster is down or not reachable.
Currently, we are setting following properties but the Producer thread is
still blocking if the Kafka cluster goes gown or unreachable.
* props.put
Hi there,
We are preparing update of our Kafka cluster and applications to Kafka
0.10.x and we have some difficulties with configuration of *Kafka
producer to be asynchronous and reliably non-blocking*.
As I understand KIP-19 (1), the main intention of Kafka developers was
to hard-limit how
Hi there,
We are preparing update of our Kafka cluster and applications to Kafka
0.10.x and we have some difficulties with configuration of *Kafka
producer to be asynchronous and reliably non-blocking*.
As I understand KIP-19 (1), the main intention of Kafka developers was
to hard-limit how
Hi,
I have an application that needs to be low latency writing to Kafka.
With the 0.81 producer I set queue.buffering.max.messages to the number of
messages I would like to producer to store in memory and
queue.enqueue.timeout.ms to 0 to have the producer throw an exception if the
server was
