Intended setup for multiple schema registry instances?

[Erik Forsberg]

Hi!

I read at http://docs.confluent.io/2.0.1/schema-registry/docs/design.html#single-master-architecture that the schema registry is designed around a single master architecture. That's fine.

What I don't quite get is how you are supposed to configure a setup with multiple schema registry instances running to ensure availability and balance load. 

Should multiple instances sit behind a load balancer, i.e. LVS or haproxy or similar? Or should you configure them as independent servers and provide multiple hostnames to the clients. Do the existing clients support randomly selecting one of several servers? 

Any docs on this that I've missed?

Thanks,

\Erik

[Ewen Cheslack-Postava]

Erik,

When you deploy with multiple instances, you'll need to make sure each has its own routatble hostname + port that is routable from other instances. However, from a client perspective, you can safely put them all behind a proxy, round robin DNS, etc if that makes things simpler for clients. However, the serializers will also accept a list of schema registry URLs, so this layer of indirection is not required.

-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-platf...@googlegroups.com.
To post to this group, send email to confluent...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/confluent-platform/4fa51a3e-c2ed-4235-9a2f-5f57183ef6b2%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

--

Thanks,
Ewen

[Erik Forsberg]

On Thursday, March 31, 2016 at 3:38:11 AM UTC+2, Ewen Cheslack-Postava wrote:

Erik,

When you deploy with multiple instances, you'll need to make sure each has its own routatble hostname + port that is routable from other instances. However, from a client perspective, you can safely put them all behind a proxy, round robin DNS, etc if that makes things simpler for clients. However, the serializers will also accept a list of schema registry URLs, so this layer of indirection is not required.

Aha! I see now that the documentation says "forward" while my brain read it as "redirect" and that gave me the wrong idea. 

Thanks!

\EF

[patel bharat]

HI I have 2 schema registry instances behind AWS ELB. Both the instances have same schema-registry.properties file. both connects to same zookeeper. Now if I take down one instance and try to get schemas. The schema registered by one instance can not be retrieved by other one. It is giving "schema not found" error.

How to setup schema registry in cluster mode ?