Kafka Trying to Contribute to Apache Kafka is a Complete Nightmare It has now been over three months since I submitted a KIP with a feature complete pull request. If you want to make a change that requires modification of a public API in Apache Kafka, you have to submit a Kafka Improvement Proposal. This
Kafka Error Retry Configuration in Kafka Connect Kafka Connect specifies two configuration items for retrying errors and backoff: errors.retry.timeout=-1 #number of retries (-1 for infinite retries) errors.retry.delay.max.ms=X #defaults to 1 min The documentation suggests this takes effect when an error is thrown during
Kafka Load Balancing Kafka Metadata Bootstrap Call There is plenty of documentation online on how to use a load balancer in front of a kafka cluster to either SSL terminate or provide access to a private kubernetes setup, etc... This post has nothing to do with that. The use case is
Kafka Dynamically Updating Kafka Cluster Settings with the Java API Kafka comes with a handful of bash scripts that wrap Scala code to perform a variety of actions on a Kafka cluster. kafka-configs adds/deletes dynamically available configuration items. There are three tiers of config items in Kafka: read-only: read from server.propeties on
Java Running MirrorMaker 2.0 with Confluent's Schema Registry MirrorMaker 2.0 came with the Kafka 2.4 release. I have not personally used MM1, but I have heard it was not great. MM2 seeks to solve the problems with MM1. I am using the same local two cluster setup when I tested
Kafka Running Brooklin with Confluent's Schema Registry Seems common to purchase a domain and then do nothing with it for a year, so it's time to start migrating from my previous blog home of 11 years to a platform with more flexibility and tooling. Following up on this post where we