Schema Registry: Clustered Setup

[MR]

Hello All,

Does anyone know steps that need to be performed for Clustered setup of Schema Registry. I currently have Schema Registry running on single node with listeners=http://0.0.0.0:8081 in schema-registry.properties.

Q1. If I want to bring up Schema Registry on 2nd node , do I still keep listeners=http://0.0.0.0:8081 in schema-registry.properties for 2nd node?
Q2. Below link has suggestion to make changes in connect-avro-distributed.properties . Can someone please confirm that this change is required?
https://stackoverflow.com/questions/39162459/confluent-schema-registry-cluster-mode

Thanks in advance !!

[Ewen Cheslack-Postava]

The key properties to ensure is set properly for multi-node schema registry configurations are `listeners` and `host.name`. These are what get stored in zookeeper and shared with other instances of schema registry so that write requests can be forwarded to the leader.

Q1. Keeping `listeners` set to that should be fine, but you'll need to make sure `host.name` is set such that it will be advertised as a resolvable hostname for other instances.

Q2. The link you give is covering multi-DC which is somewhat different from multiple schema registry instances in the same DC. http://docs.confluent.io/current/schema-registry/docs/deployment.html#multi-dc-setup gives guidance on multi-DC setup. Re: the guidance on modifying the properties file, it correct that you'd need to modify the URLs to match your deployment.

-Ewen

--
You received this message because you are subscribed to the Google Groups "Confluent Platform" group.
To unsubscribe from this group and stop receiving emails from it, send an email to confluent-platform+unsub...@googlegroups.com.
To post to this group, send email to confluent-platform@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/6907e9d6-2c82-430d-a92f-6c3f13a7dabf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.