Re: vpn vs TimeoutException

Is this maybe related to https://issues.apache.org/jira/browse/KAFKA-3686 or https://issues.apache.org/jira/browse/KAFKA-4089 ? Thanks, - Sini From: Peter Sinoros Szabo/Hungary/IBM To: users@kafka.apache.org Date: 2017/05/25 17:01 Subject:vpn vs TimeoutException Hi, Please

Re: vpn vs TimeoutException

Hi, Do you know if a retry tries to use the same Broker connection or may reinitialize that connection too? Thanks, - Sini From: "Peter Sinoros Szabo" To: users@kafka.apache.org Date: 2017/05/25 17:01 Subject:vpn vs TimeoutException Hi, Please help me to unde

vpn vs TimeoutException

Hi, Please help me to understand the following situation and to fix the problem. My servers needs a vpn connection to access the kafka brokers. The vpn connection restarts periodically and in some of these cases, the kafka producer send call's callback return with TimeoutExceptions. I'd like to

Re: Order of punctuate() and process() in a stream processor

p.m., Peter Sinoros Szabo wrote: Hi, I see, now its clear why the repeated punctuations use the same time value in that case. Do you have a JIRA ticket to track improvement ideas for that? It would be great to have an option to: - advance the stream time before calling the process() on a new

Re: Order of punctuate() and process() in a stream processor

ation and time management already, and it seems to be another valuable improvement. -Matthias On 5/12/17 10:07 AM, Peter Sinoros Szabo wrote: > Well, this is also a good question, because it is triggered with the same > timestamp 3 times, so in order to create my update for both three seconds,

RE: Order of punctuate() and process() in a stream processor

t;. But atm, we just don't do this. Does this make sense? Is this critical for your use case? Or do you just want to understand what's happening? -Matthias On 5/12/17 8:59 AM, Peter Sinoros Szabo wrote: > Hi, > > > Let's assume the following case. > - a stream proces

Re: Order of punctuate() and process() in a stream processor

ign and include scheduled punctuations when advancing "streams time". But atm, we just don't do this. Does this make sense? Is this critical for your use case? Or do you just want to understand what's happening? -Matthias On 5/12/17 8:59 AM, Peter Sinoros Szabo wrote: >

Order of punctuate() and process() in a stream processor

Hi, Let's assume the following case. - a stream processor that uses the Processor API - context.schedule(1000) is called in the init() - the processor reads only one topic that has one partition - using custom timestamp extractor, but that timestamp is just a wall clock time Image the followin

500ms FetchConsumer RemoteTimeMs

Hi, I am setting up metrics monitoring on a new Kafka 0.10.0.1 cluster and observed the following: - kafka.network:type=RequestMetrics,name=TotalTimeMs,request=Produce 's 99th percentile is 18.71ms (remote=15.71, response send time, local and queue times are both 1ms), so far this seems to be

kafkaproducer send blocks until broker is available

Hi, I'd like to use the Java Kafka producer in a non-blocking async mode. My assuptions were that until the new message can fit into the producer's memory, it will queue up those messages and send out once the broker is available. I tested a simple case when I am sending messages using KafkaPro

monitor page cache read ratio

Hi, As I read more and more about kafka monitoring it seems that monitoring the linux page cache hit ration is important, but I do not really find a good solution to get that value. Do you have a good practice how to get that value? Regards, Peter