Which schema you are using depends on how it is configured your solrconfig.xml file (i.e. if you have explicitly declared the ClassicIndexSchemaFactory or not). If not Solr will assume it is managed, and create a managed_schema from your schema.xml file, at which point your schema.xml file is no longer read from. The managed-schema will be read from at this point forward. Further changes to schema.xml will be ignored.
On Wed, Sep 27, 2023 at 11:01 AM Jim Morgan <jim.mor...@nknews.org.invalid> wrote: > Wait! Progress! > I have no idea if this is the right way to do things, but I copied the > entire core over, conf and data directories. Then I created a core on the > new server, but put the conf location as conf/solrconfig.xml, and the > schema location as conf/managed-schema (seems someone had renamed it from > schema.xml. > So now its running at least on 8.11. Will try more tomorrow > > On Wed, Sep 27, 2023 at 4:16 PM Jim Morgan <jim.mor...@nknews.org> wrote: > > > OK, so I had some more time to work on this. I removed version 9.3 and > > tried with version 8.11. But still the same story: any of the API restore > > methods I try are rejected. > > > > I have also tried stopping solr, copying the whole > > /var/solr/data/collectionname directory from old server to new server, > and > > restarting. Nothing happens. The core doesn't appear on the new server. > > > > Manually creating /var/solr/data/collectionname and copying the conf > > directory into it doesn't do anything either. > > > > I have also tried creating a core on the new server. That also fails as > it > > can't find solrconfig.xml, but does create a /var/solr/data/corename > > directory. > > > > I'm just drawing blanks everywhere. What next? > > > > On Mon, Sep 25, 2023 at 5:26 PM Vincenzo D'Amore <v.dam...@gmail.com> > > wrote: > > > >> In the past, when upgrading to a major version, well... sometimes it > >> happened, you can even have a loss of performance. > >> So before moving I would be sure if I can and what I gain from it. > >> For example in the Solr 9.x the Data Import Handler has been moved out > to > >> an external component, still open source but it is external. > >> > >> On Mon, Sep 25, 2023 at 11:13 AM Jim Morgan > <jim.mor...@nknews.org.invalid > >> > > >> wrote: > >> > >> > Thanks. Good tip for the logs. Although they didn't prove very useful > in > >> > determining what the problem with the import was: absolutely nothing > was > >> > logged! > >> > > >> > Server load: I have that under control in terms of RAM and hard disk > >> space > >> > and that won't be an issue. Is there a command to find out how many > >> > requests are being processed? Or any useful stats/status summary. Or > do > >> you > >> > mean use grep and wc on logs ... also can do, but as I'm learning > about > >> > Solr I'm keen to learn the tricks. > >> > > >> > Moving to the latest version was basically me trying to get as much > >> done in > >> > one disruption as possible. We have to do the migration, so I figured > we > >> > should try to move to the latest solr version as well. If we can't do > >> it, > >> > then I'll take the latest 8.x version, sure, but I thought I'd try. > >> > > >> > On Mon, Sep 25, 2023 at 4:59 PM Vincenzo D'Amore <v.dam...@gmail.com> > >> > wrote: > >> > > >> > > :) > >> > > 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 > >> > <jim.mor...@nknews.org.invalid > >> > > > > >> > > 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 < > >> v.dam...@gmail.com> > >> > > > 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 > >> > > <jim.mor...@nknews.org.invalid > >> > > > > > >> > > > > 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 > >> > > > >> > > >> > >> > >> -- > >> Vincenzo D'Amore > >> > > > -- Vincenzo D'Amore
