From 457eb113f4db0c29579b31f17aa5b51cba47c2bc Mon Sep 17 00:00:00 2001 From: Saravanan Raju Date: Sat, 6 Apr 2019 12:18:34 +0530 Subject: [PATCH] MINOR : Doc for running schema registry behind a load balancer (#546) MINOR : Doc for running schema registry behind a load balancer (#546) --- docs/install.rst | 25 +++++++++++++++++++++++++ 1 file changed, 25 insertions(+) diff --git a/docs/install.rst b/docs/install.rst index 062f1f5b0..0e69f409e 100644 --- a/docs/install.rst +++ b/docs/install.rst @@ -166,3 +166,28 @@ Edit the following section to add appropriate database and user settings 6. Start the registry server ``sudo ./bin/registry start`` + + +Running Schema Registry with a load balancer +--------------------------------------------- + + One or more schema registry instances can be put behind a load balancer for reverse proxying, in that case appropriate schema registry url +must be mentioned in the load balancer's configuration file. For example, in case of Apache mod proxy the VirtualHost tag in the +configuration file should be edited out with the following + + + + BalancerMember http://127.0.0.1:9090 + BalancerMember http://127.0.0.2:9090 + + + ProxyPreserveHost On + + ProxyPass / balancer://mycluster/ + ProxyPassReverse / balancer://mycluster/ + + + In case of serializers and deserializers the parameter "schema.registry.url" can be pointed to the loader balancer's url or it can be a list of +schema registry severs with "schema.registry.client.url.selector" set to one of "FailoverUrlSelector" , "LoadBalancedFailoverUrlSelector" +or "RoundRobinUrlSelector". The parameter "schema.registry.client.url.selector" defines the retry strategy in the case the currently picked +schema registry server from the list of schema registry servers is not reachable. \ No newline at end of file