lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Peter Wolanin (JIRA)" <>
Subject [jira] Commented: (SOLR-2044) Replication ping.jsp page for use with Amazon EC2 and Multiple Cores
Date Sat, 09 Oct 2010 00:28:30 GMT


Peter Wolanin commented on SOLR-2044:

There is already a "health check" functionality - seems like this might be combined?  Or instead
you might have an external script which does this same check and sets or removes the health
check file?

> Replication ping.jsp page for use with Amazon EC2 and Multiple Cores
> --------------------------------------------------------------------
>                 Key: SOLR-2044
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: replication (java)
>    Affects Versions: 1.4.1
>            Reporter: Bill Bell
>             Fix For: 1.4.2
>         Attachments: ping.jsp
> When hosting SOLR at Amazon there is an issue with load balancing and replication. This
is especially useful when you are using multiple slaves behind
> the load balancer and a MASTER SOLR box. The Load Balancer at Amazon has no way of knowing
that each SLAVE has data from the MASTER replicated. As soon as the instance starts, 
> Amazon starts sending requests to the Slaves. You need to have the Slave running in order
to get the files from the Master.
> The solution is to add a ping.jsp page that Amazon hits on the Slave Tomcat/Jetty instances.
The ping.jsp checks all cores to make sure they all have data, otherwise it returns a non-200
values which signals Amazon
> to not send requests to the Slaves.
> Put this into your solr.war file as /admin/replication/ping.jsp

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message