ID ranges in Schema Registry
You can avoid overlapping IDs for Schema Registry entities across different Schema Registry instances by setting ID ranges in each instance.
If your deployment has many Schema Registry instances in different clusters, you can ensure that each Schema Registry instance operates in a preset ID range so that there are no overlapping IDs. To achieve this, you need to set an ID range.
When an ID range is set, each Schema Registry entity (schema metadata, branches, versions, and so on) is created with an ID that falls within the configured range. Configuring a range can simplify schema export and import between Schema Registry instances where conflicting IDs can cause the import process to fail.
Consequently, having non-overlapping ID ranges allocated to each Schema Registry makes data replication easier when schema IDs are embedded in the data. This is important because replicated data can only be deserialized with compatible schemas on the replication target site.