Hi Mathias,
Looking at that thread dump, I think the potential culprit is this one:
TRACE 303545: (thread=200049)
sun.nio.ch.EPollArrayWrapper.epollWait(EPollArrayWrapper.java:Unknown line)
sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:269)
sun.nio.ch.EPollSelectorImpl.doSelect(EP
I use a simple email client (Thunderbird) and have a filter setup so
that mails to the Kafka user mailing list are moved to a specific
folder. I then have "thread view" enabled so that the replies/discussion
shows up in the right context. I have the same for some other mailing
lists too and hav
+1 (binding). Verified quickstart and unit tests ran ok.
On Sun, Feb 1, 2015 at 9:11 AM, Steven Wu wrote:
> In Netflix, we have been using route53 DNS name as bootstrap servers in AWS
> env. Basically, when a kafka broker start, we add it to route53 DNS name
> for the cluster. this is like the V
In Netflix, we have been using route53 DNS name as bootstrap servers in AWS
env. Basically, when a kafka broker start, we add it to route53 DNS name
for the cluster. this is like the VIP that Jay suggested.
But we are also moving toward to use Eureka service registry for
bootstrapping. We are worr
Hi there,
As far as I know, RequestTimedOut is returned exclusively when the
`Timeout` value provided in a Produce Request is exceeded. The message
will likely still be committed on the local broker, but it means that
some replicas may not have received it yet. I'm honestly not sure what
the use c
You may already know this but the producer doesn't require a complete list
of brokers in its config, it just requires the connection info for one
active broker which it uses to discover the rest of the brokers. We allow
you to specify multiple urls here for failover in cases where you aren't
using
Jun:
You raise a very good question: let me explain why we use
Broker.getConnectionString(), so may be we'll get a supported way to
answer our need.
We use Broker.getConnectionString() because we deploy "Kafka services"
in Amazon EC2 with the following architecture:
* Three VMs dedicated to Zooke
