Great feedback, thanks. So the multi-core structure I have then is a single Solr server set up, essentially hosted by one domain owner (but to be used by both). My question is how does that Solr server connect to the 2 Web applications to create the 1 master index (to be used when searching on either Web app)? It feels like I just reference the Solr server from within the Web app search templates (e.g. PHP files). That is logical in terms of pulling the data into the Web apps, but it's still not clear to me how the data from those 2 Web apps actually gets into the Solr server if Solr server doesn't live on the same server as the Web app(s). Any thoughts?
On Wed, Nov 6, 2013 at 10:57 PM, Shawn Heisey <s...@elyograg.org> wrote: > On 11/6/2013 11:38 PM, Rob Veliz wrote: > > Trying to find specific information to support the following scenario: > > > > - I have one site running on one server with marketing content, blog, > etc. > > I want to index. > > - I have another site running on Magento on a different server with > > ecommerce content (products). > > - Both servers live in completely different environments. > > - I would like to create one single search index between both sites and > > make that index searchable from both sites. > > > > I think I can/should use the multi-core approach and spin off a new > server > > to host Solr but can anyone verify this is the best/most appropriate > > approach? Are there any other details I need to consider? Can anyone > > provide a step by step for making this happen to validate my own > technical > > plan? Any help appreciated...was initially thinking I needed SolrCloud > but > > that seems like overkill for my primary use case. > > SolrCloud makes for *easy* redundancy. There is a three-server minimum > if you want it to be fault-tolerant for both Solr and Zookeeper. The > third server would only run zookeeper and could be an extremely > inexpensive machine. The other two servers would run both Solr and > Zookeeper. Redundancy without cloud is possible, it's just not as > automated, and can be done with two servers. > > It is highly recommended that redundant servers are not separated > geographically. This is especially important with SolrCloud, as > Zookeeper redundancy requires that a majority of the servers be > operational. That can be extremely difficult to guarantee in a > multi-datacenter model, if one assumes that an entire datacenter can > disappear from the network. > > If you don't care about redundancy, then you'd just run a single server, > and SolrCloud wouldn't provide much benefit. > > Multiple cores is a good way to go -- the two indexes would be logically > separate, but you'd be able to use either one. With SolrCloud, it would > be multiple collections. > > Thanks, > Shawn > > -- *Rob Veliz*, Founder | *Mavenbridge* | rob...@mavenbridge.com | M: +1 (206) 909 - 3490 Follow us at: http://twitter.com/mavenbridge
