You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2012/06/14 03:42:42 UTC
[jira] [Updated] (SOLR-2044) Replication ping page for use with
Amazon EC2 and Multiple Cores
[ https://issues.apache.org/jira/browse/SOLR-2044?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Hoss Man updated SOLR-2044:
---------------------------
Fix Version/s: (was: 4.0)
Summary: Replication ping page for use with Amazon EC2 and Multiple Cores (was: Replication ping.jsp page for use with Amazon EC2 and Multiple Cores)
Removing fix version since this issue hasn't gotten much attention lately and doesn't appear to be a priority for anyone for 4.0.
As always: if someone wants to take on this work they are welcome to do so at any time and the target release can be revisited
---
In particular, JSP support has been removed from solr -- largely to ensure that the data available in the Admin UI is always available via handlers -- so the patch would need to be reworked into handler code of some kind.
My suggestion would be to add this logic directly into the ReplicationHandler as an option that causes a failure if the indexversion is "0".
> Replication ping page for use with Amazon EC2 and Multiple Cores
> ----------------------------------------------------------------
>
> Key: SOLR-2044
> URL: https://issues.apache.org/jira/browse/SOLR-2044
> Project: Solr
> Issue Type: Bug
> Components: replication (java)
> Affects Versions: 1.4.1
> Reporter: Bill Bell
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org