# Confluent SchemaRegistry taking to long to catch up with offsets during startup

**URL:** https://forum.confluent.io/t/confluent-schemaregistry-taking-to-long-to-catch-up-with-offsets-during-startup/10943
**Category:** Schema Registry
**Created:** [24 June 2024 06:47 UTC](https://forum.confluent.io/t/confluent-schemaregistry-taking-to-long-to-catch-up-with-offsets-during-startup/10943 "2024-06-24T06:47:44Z")
**Posts on this page:** 1
**Page:** 1

<div class="post-metadata">

### Author: ![bijoy.computers](https://avatars.discourse-cdn.com/v4/letter/b/e274bd/32.png) [@bijoy.computers](https://forum.confluent.io/u/bijoy.computers)
#### Post date: [24 June 2024 06:47 UTC](https://forum.confluent.io/t/confluent-schemaregistry-taking-to-long-to-catch-up-with-offsets-during-startup/10943/1 "2024-06-24T06:47:44Z")

</div>

Hi,

I have deployed confluent schema registry version 7.6.0 on my on-premise Kubernetes cluster,and it is pointing to \_schemas topic in Kafka cluster hosted to Confluent cloud on GCP.

The\_schemas topic is having around 21000+ schema entries.

When the schema registry instance is started for the first,it is taking almost 6-7 mins to start.From the logs I can see that this time is taken to catch up with those 21000+ offsets.Below is the logs snippet:

# ===================================== [2024-06-21 18:00:22,567] INFO Kafka store reader thread starting consumer (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:135) [2024-06-21 18:00:23,127] INFO Seeking to beginning for all partitions (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:181) [2024-06-21 18:00:23,129] INFO Initialized last consumed offset to -1 (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:185) [2024-06-21 18:00:23,132] INFO [kafka-store-reader-thread-\_schemas]: Starting (io.confluent.kafka.schemaregistry.storage.KafkaStoreReaderThread:127) [2024-06-21 18:00:24,012] INFO Wait to catch up until the offset at 21291 (io.confluent.kafka.schemaregistry.storage.KafkaStore:313)

After the last line in above logs,its stuck for about 6-7 mins,after which the schema registry finally starts listening to requests.

Could you please let us know what could be the reason for such a delay,and how to fix it?

FYI,we have dedicated connection between our on-prem environment and the confluent cloud hosted on GCP.