Skip to content

Commit

Permalink
MINOR : Doc for running schema registry behind a load balancer (#546)
Browse files Browse the repository at this point in the history
MINOR : Doc for running schema registry behind a load balancer (#546)
  • Loading branch information
raju-saravanan authored and guruchai committed Jul 11, 2019
1 parent bbc990e commit 457eb11
Showing 1 changed file with 25 additions and 0 deletions.
25 changes: 25 additions & 0 deletions docs/install.rst
Original file line number Diff line number Diff line change
Expand Up @@ -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

<VirtualHost *:80>
<Proxy balancer://mycluster>
BalancerMember http://127.0.0.1:9090 <!-- First schema registry server -->
BalancerMember http://127.0.0.2:9090 <!-- Second schema registry server -->
</Proxy>
ProxyPreserveHost On

ProxyPass / balancer://mycluster/
ProxyPassReverse / balancer://mycluster/
</VirtualHost>

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.

0 comments on commit 457eb11

Please sign in to comment.