Open Norsu296 opened 1 year ago
Did you check the network between each sr instance
Did you check the network between each sr instance
I have only one sr instance
I suggest setting SCHEMA_REGISTRY_DEBUG=true
and editing your log4j config to get more information.
@Norsu296 did u solve?
@Norsu296 did u solve?
No. I upgraded kafka to 3.4.1 and schema registry to newest version and also I increased cpu resources for schema and its a little faster but still sometimes rebalancing takes few hours. In schema debug logs i dont see anything useful. In kafka logs after upgrade I can see log with information about expired heartbeat from schema.
Hello, I have problem with schema-registry, I run it on clean kubernetes cluster where installed is only Kafka Cluster, zookeeper and schema-registry. Brokers are running, I can connect to them and send/read messages from topics. When schema-registry is starting I can see info in logs as below:
Schema-registry after few restarts starts working but I don't understand why it happens on clean clusters and I have to wait about 30-60 minutes when it will be ready. I'm using
confluentinc/cp-schema-registry:7.3.2
. Also in brokers logs I don't see any useful informations. Broker logs:My schema-registry configuration:
Also I noticed when cluster is upgrading and brokers are down schema-registry is also in infinite rebalancing and it ends when I manually delete pod. How can I resolve this issue?