Hi,
We are seeing a weird behavior for deleted topics on our cluster. Broker
logs have following messages, the cluster appears to be healthy except for
these messages.
ERROR [ReplicaFetcher replicaId=1, leaderId=5, fetcherId=0] Error for
partition deleted-topic-20 to broker
5:org.apache.kafka.com
You should look at the kafka-connect-jdbc code. It is a kafka connector to
load data into a relational database.
https://github.com/confluentinc/kafka-connect-jdbc
The documentation is here -
https://docs.confluent.io/current/connect/connect-jdbc/docs/index.html
On Fri, Oct 13, 2017 at 12:29 P
You should look at the kafka-connect-jdbc code. It is a kafka connector to
load data into a relational database.
https://github.com/confluentinc/kafka-connect-jdbc
The documentation is here -
https://docs.confluent.io/current/connect/connect-jdbc/docs/index.html
On Fri, Oct 13, 2017 at 12:29 P
The error seems pretty obvious. Is your zookeeper address correct and is it
running?
On Tue, Oct 10, 2017 at 3:35 PM, Kannappan, Saravanan (Contractor) <
saravanan_kannap...@comcast.com> wrote:
> Hello, Someone can you help me kafka server not starting after rebooting ,
> the below is the error m
There is a a native kafka framework which runs on top of DC/OS.
https://docs.mesosphere.com/service-docs/kafka/
This will most likely be a better way to run kafka on DC/OS rather than
running it as a marathon framework.
On Mon, Oct 2, 2017 at 7:35 AM, David Garcia wrote:
> I’m not sure how y
