;
Date: Wednesday, December 7, 2016 at 1:02 PM
To: Phillip Mann <pm...@trulia.com>
Cc: "users@kafka.apache.org" <users@kafka.apache.org>
Subject: Re: Creating a connector with Kafka Connect Distributed returning 500
error
The bug I was referring to was only in trunk for just a w
The bug I was referring to was only in trunk for just a while. Thus, your
issue must be related to something else, even though the response statuses
are similar.
Let me know if you want to share a bigger and more detailed (DEBUG level at
least) snapshot of the parts of the logs that might be
Hello Konstantine,
Thanks for your reply.
I am using Confluent 3.0.1 installed on my machine and our cluster. However,
our AWS cluster has Confluent 3.1.1 installed so I will test with 3.1.1 client
and cluster and see if this resolves the issue. Additionally, I’ll use the
debug levels if
Hi Phillip,
may I ask which Kafka version did you use?
trunk repo in Apache Kafka contained briefly a bug in Connect framework
(during the past week) that produced failures similar to the one you
describe (only in distributed mode). A fix has been pushed since yesterday.
3) Some useful
I am working on migrating from Camus to Kafka Connect. I am working on the
implementation of Kafka Connect and specifically focused on distributed mode. I
am able to start a worker successfully on my local machine which I assume
communicates with my Kafka cluster. I am further able to run two
