I'm trying to use the SimpleConsumer to consume a queue, using long polling.
I'm encountering some difficulties when using very long poll times (60s or
more). It seems to be conflicting with the socket timeout.
I thought the socket timeout was the timeout to actually connect to the broker,
then
Yes, it's a bit confusing. maxWait controls how long a fetch request will
wait on the broker in the normal case. The issue is that if there is a hard
crash on the broker (host is down), the client may not realize this
immediately since TCP will try very hard to maintain the socket connection.
By se
> case. Typically, SocketTimeout should be set to be at least maxWait or a
> bit larger.
The consumer-config documentation states that "The actual timeout set
will be max.fetch.wait + socket.timeout.ms." - however, that change
seems to have been lost in the code a while ago. I'll file a jira for
I want to use a ZK cluster for my Kafka cluster, which is only available over a
cross-country VPN tunnel. The VPN tunnel is prone to resets, every other day or
so, perhaps down for a couple of minutes at a time.
Is this a concern? Any setting changes I should make to mitigate any potential
is
