Thanks, Mark. That does remove the node. And it seems to do so permanently. Even when I restart Solr after unloading, it does not join the SolrCloud cluster. And I can get it to re-join the cluster by creating the core.
Anyone know if there is an API to determine the state of a node. When AWS auto scaling add a new node, I need to make sure it has before active before I enable it in the load balancer. Bill On Thu, Jan 3, 2013 at 9:10 AM, Mark Miller <markrmil...@gmail.com> wrote: > > http://wiki.apache.org/solr/CoreAdmin#UNLOAD > > - Mark > > On Jan 3, 2013, at 9:06 AM, Bill Au <bill.w...@gmail.com> wrote: > > > Mark, > > What do you mean by "unload them"? > > > > I am using an AWS load balancer with my auto scaling group in stead of > > using Solr's built-in load balancer. I am no sharding my index. I am > > using SolrCloud for replication only. I am doing local search on each > > instance and sending all updates to the shard leader directly because I > > want to minimize traffic between nodes during search and update > > > > Bill > > > > > > On Wed, Jan 2, 2013 at 6:47 PM, Mark Miller <markrmil...@gmail.com> > wrote: > > > >> > >> On Jan 2, 2013, at 5:51 PM, Bill Au <bill.w...@gmail.com> wrote: > >> > >>> Is anyone running Solr 4.0 SolrCloud with AWS auto scaling? > >>> > >>> My concern is that as AWS auto scaling add and remove instances to > >>> SolrCloud, the number of nodes in SolrCloud Zookeeper config will grow > >>> indefinitely as removed instances will never be used again. AWS auto > >>> scaling will keep on adding new instances, and there is no way to > remove > >>> them from Zookeeper, right? > >> > >> You can unload them and that removes them. > >> > >>> What's the effect of have all these phantom > >>> nodes? > >> > >> Unless they are only replicas, they would need to be removed. > >> > >> Also, unless you are using elastic ips, > >> https://issues.apache.org/jira/browse/SOLR-4078 may be of interest. > >> > >> - Mark > >
