:) looking at solr.log you can see the requests and, even if you cannot be completely sure, which core is currently receiving requests. Before moving to a new solr version I should understand how is your server average load, how many requests per second your server is handling. Honestly I'm not sure that moving to the latest solr version is a good idea, what do you think to gain moving immediately to the latest version? Maybe better move to the latest solr 8 version
On Mon, Sep 25, 2023 at 10:10 AM Jim Morgan <[email protected]> wrote: > Quick response! There are two cores. But I think only one of them is > actively in use. I think the other one doesn't need to be migrated. But > will know for sure when I manage it and can test the app with the new > server! > Core in use seems to be about 12Gb. > > On Mon, Sep 25, 2023 at 3:48 PM Vincenzo D'Amore <[email protected]> > wrote: > > > Hi Jim, > > > > how many cores (indexes) do you have in this Solr server? > > > > On Mon, Sep 25, 2023 at 9:41 AM Jim Morgan <[email protected] > > > > wrote: > > > > > Hi, > > > I inherited a solr installation from a previous sysadmin, and we'd like > > to > > > see if we can move it from the current server to a new one. I don't > have > > > much knowledge of solr, but I know my way around Linux. Apologies in > > > advance for any dumb questions, and please feel free to educate me. > > > > > > Old install is Solr 8.5 running on Ubuntu 18. We're thinking that while > > we > > > are switching servers, we might as well try to upgrade to Ubuntu 22 and > > > Solr 9.3 (with corresponding JVM increase to 11). > > > First question, is that a crazy idea? Or should we be moving to the > same > > > version of Solr on the new server, and then upgrade in place. We'd > prefer > > > to do it with minimal downtime, so setting up parallel servers and > > > migrating the data across seems like the least disruptive. > > > > > > So I have tried the parallel server approach. No issues installing Solr > > and > > > JVM. From reading around the web, starting with > > > > > > > > > https://solr.apache.org/guide/solr/latest/deployment-guide/backup-restore.html > > > And several other pages, which all seem to repeat the advice, the > backup > > > restore process is simple. This is a standalone install so I should use > > > > > > > > > > > > http://localhost:8983/solr/collname/replication?command=backup&location=/snapshots > > > > > > to backup, which works fine: the backup appears in /snapshots/ as > > > snapshot.2023xxx. All good. > > > > > > I take the backup, and copy it to the new server, and put it in the > same > > > location, /snapshots/2023xxx > > > Then apparenly I only need to run > > > > > > > > > > > > http://localhost:8983/solr/collname/replication?command=restore&name=snapshot.2023xxx&location=/snapshots > > > > > > But this doesn't work. I've tried a lot of different variations, > > combining > > > snapshot name and location, with or without the collection name, but > all > > I > > > get is the zen like error > > > Searching for Solr? > > > You must type the correct path. > > > Solr will respond. > > > > > > So that's where I'm at. I'm wondering if I've missed a step that's > > obvious > > > to Solr veterans, but which is missing from the backup/restore page. > > > Do I need to create the core first, for example. Or create the core and > > > copy config files over to the new server. > > > > > > > > > -- > > Vincenzo D'Amore > > > -- Vincenzo D'Amore
