Dear Solr Community,
I am a Solr newbie, and have spent quite a few hours (across a couple of days)
trying to research this, but am not quite sure what direction to go in, so
would appreciate any suggestions.
I think I am getting confused between differences in Solr versions (most links
seem to talk about Solr 6, and I’ve installed Solr 9), and SolrCloud vs.
Standalone, when searching the ’Net … so I am hoping that someone can point me
towards what I need to do. Apologies in advance for perhaps not using the
correct Solr terminology.
I will describe what I have, and what I want to accomplish, to the best of my
abilities.
I have installed Solr 9.2.1 on two separate physical nodes (different physical
computers). Both are running SolrCloud, and are running with the same
(duplicate) configuration files. Both are running their own local zookeeper,
and are separate cores. Let’s call them solr1 and solr2. Right now I can
index content on and search each one individually, but they do not know about
each other (which is I think the fundamental problem I am trying to solve).
My goal is to replicate content from one to the other, so that I can take one
down (e.g., solr1) and still search current collections (e.g., on solr2). When
I run Solr Admin web page, I can select: Collections=> {collection}, click on a
Shard, and I see the [+ add replica] button, but I can’t add a new replica on
the “other" node, because only the local node appears (e.g.,
10.0.x.xxx:8983_solr). What I think I need to do is add the nodes (solr1 and
solr2) together (?) so that I can add a new replica on the “other” node.
I’ve found references that tell me I need an odd number of zookeeper nodes (for
quorum), so I’m not sure if I want both nodes to share a single zookeeper
instance? If I did do that, and let’s say that I pointed solr2 to zookeeper on
solr1, could I still search against solr2 if solr1 zookeeper was down? I would
think not, but I’m not sure.
FWIW - this is NOT a high volume application, or an enterprise application, but
I want to be able to take one node down — e.g., for maintenance or upgrades or
backups — and not lose all of my search capabilities.
The gist of the problem, I think, is that Cloud => Nodes only shows the local
node, as does Cloud => Graph for each shard. I am trying to figure out how to
replicate shards across both nodes, so that they are in-sync. Ideally I’d like
to be able to update from either, but if I have to designate one as master for
updating and one as slave, I can probably live with that, as long as I could
still search on the master. Although from what I’ve read, I think (?) that
with SolrCloud that master/slave concept goes away, and one node now becomes a
leader? But I may be confused about that ...
Nonetheless, I think I am also getting confused with terminology, and what I’m
looking for the easiest (? best? most straight forward?) path so that I can
search against either node if one is down, and still return search against the
most current collection data. What is the best way to make that happen?
Comments? Suggestions?
Thanks,
Dave.
