> but it’s not directly tied to a quorum mechanism
Correct.
> this doesn’t really differ from having only three brokers
Also correct.
However, practically, we often reassign failed replicas to another broker
(e.g. using CruiseControl) in case of broker crash so having 3 + 1 brokers
is more safe.
Hi Kafka Team,
We’re upgrading from Kafka v3.7.1 to v3.9.0 and encountered issues with our
custom Kafka Authorizer that extends AclAuthorizer. Starting with Kafka v3.8.0,
methods like logAuditMessage and isSuperUser in AclAuthorizer were made
private, which breaks our implementation.
1. Is th
Hello All,
Can we have multiple Kafka clusters using a single Schema Registry (either
Karapace ? If anyone has set up a similar system, pls let me know.
Thanks!
Hi Karan, good question! I’ve asked our Kafka dev team and they think it may be
possible in theory, but depending on if you are using a managed Kafka service
maybe not supported – e.g. NetApp Instaclustr managed Kafka supports Karapace,
but not with multiple clusters.
Good luck, Paul Brebner
F
Actually schema registry is backed by topics on one Kafka cluster. Applications
using it can be where you want using this particular cluster or not. Or maybe
not even using Kafka ;)
--
Raphael Mazelier
Sent from Proton Mail Android
Original Message
On 1/7/25 23:25, karan ala
Nothing prevents you from using the same schema registry for multiple
clusters AFAIK - I used the Confluent schema registry with multiple
clusters in the past
On Tue, Jan 7, 2025 at 5:25 PM Brebner, Paul
wrote:
> Hi Karan, good question! I’ve asked our Kafka dev team and they think it
> may be p
