On 12/22/2013 2:10 PM, David Santamauro wrote: > My goal is to have a redundant copy of all 8 currently running, but > non-redundant shards. This setup (8 nodes with no replicas) was a test > and it has proven quite functional from a performance perspective. > Loading, though, takes almost 3 weeks so I'm really not in a position to > redesign the distribution, though I can add nodes. > > I have acquired another resource, a very large machine that I'd like to > use to hold the replicas of the currently deployed 8-nodes. > > I realize I can run 8 jetty/tomcats and accomplish my goal but that is a > maintenance headache and is really a last resort. I really would just > like to be able to deploy this big machine with 'numShards=8'. > > Is that possible or do I really need to have 8 other nodes running?
You don't want to run more than one container or Solr instance per machine. Things can get very confused, and it's too much overhead. Also, you shouldn't start Solr with the numShards parameter on the commandline. That should be given when you create each collection. With existing collections, you can simply run the CoreAdmin CREATE action on the new node with more resources. http://wiki.apache.org/solr/SolrCloud#Creating_cores_via_CoreAdmin So you'd do something like this, once for each of the 8 existing parts: http://newnode:port/solr/admin/cores?action=CREATE&name=collname_shard1_replica2&collection=collname&shard=shard1 It will automatically replicate the shard from its current leader. One thing to be aware of: With 1.4TB of index data, it might be impossible to keep enough of the index in RAM for good performance, unless the machine has a terabyte or more of RAM. http://wiki.apache.org/solr/SolrPerformanceProblems#OS_Disk_Cache Thanks, Shawn
