Thanks community! That helps! To check practically, I have now setup Solr 3.5 in test environment. Few observations on that,
1. I simply copy-pasted one of the Solr 1.4 instance on Solr 3.5 setup (after correcting schema.config and solr.config files based on what is suited for 3.5). If I do query like, http://myserver:8080/solr/Solr_3.5_Instance/select?q=test&shards=myserver:8080/solr/Solr_3.5_Instance, myserver:8080/solr/Solr_1.4_Instance, then it works OK! So, now, wondering, index format has been changed after Solr 1.4, and hence, I was expecting above search to fail. Am I correct? 2. Continuing above point, I guess, if I need to use new feature which didn't exist in Solr 1.4, but exists in Solr 3.5, then this hybrid (1.4 and 3.5 solr instances) setup won't work. Any thoughts? 3. I got wind that, first commit would convert Solr 1.4 index to new format in Solr 3.5 setup. Is it so? 4. Are there any migration tool (or any other means?) available that would convert old indexes (1.4) to new format (3.5)? Kind regards, Bhavnik -------- Original Message -------- To supplement the responses you have already gotten: All servers involved in a distributed query, including the one that is accessed and all the shards that are accessed from it, must run the same Javabin version. Solr 1.4.1 and earlier use javabin version 1 and everything newer uses javabin version 2. What you are proposing above will not work. Hopefully you have two complete sets of servers, for redundancy. It would be a good idea to upgrade one server set, then upgrade the other. SOLR-2204 is in the works to make it possible to have these versions work together. I don't think it's been committed yet. Thanks, Shawn > > > Subject: Re: Migration from Solr 1.4 to Solr 3.5 Date: Fri, 23 Dec 2011 > 10:58:43 -0800 From: Siva Kommuri > <snv.komm...@gmail.com><snv.komm...@gmail.com> Reply-To: > solr-user@lucene.apache.org To: solr-user@lucene.apache.org > <solr-user@lucene.apache.org> <solr-user@lucene.apache.org> CC: > solr-user@lucene.apache.org > <solr-user@lucene.apache.org><solr-user@lucene.apache.org> > > One migration strategy is to fall back to XML parser from the javabin parser, > upgrade Solrj jars to 3.4, turn off replication, upgrade master, upgrade each > of the slaves while turning on replication. Once all slaves have been > upgraded/replication turned on - switch back to javabin parser. > > Best wishes, > Siva on 3GS > > On Dec 23, 2011, at 7:52, Erick Erickson <erickerick...@gmail.com> > <erickerick...@gmail.com> wrote: > > > Have you looked at CHANGES.txt in <SOLR_HOME>? It has upgrade > > instructions for every release. Note that in general, newer Solr will *read* > > an older index (one major revision back. i.e. 3.x should read 1.x, but 4.x > > will not read 1.x. Note also that there was no 2.x solr). > > > > The cautions in the upgrade notes are really about making sure that an > > index *produced* with 3.x is not *read* by 1.4, i.e. don't upgrade the > > master before the slave. > > > > I *think* that as long as you upgrade *all* slaves before upgrading the > > master, you'll be fine. And I also believe that you can upgrade only some > > of the slaves. Each of the slaves, even if only some of them are > > upgraded, are reading a 1.4 index even after replications. > > > > But I'd test first. And if you can re-index, that would actually be the best > > solution. However, as above you can't reindex until *all* the slaves > > are upgraded. > > > > Best > > Erick > > > > On Fri, Dec 23, 2011 at 7:41 AM, Bhavnik Gajjar <bhavnik....@gmail.com> > > <bhavnik....@gmail.com> wrote: > >> Greetings, > >> > >> We are planning to migrate from Solr 1.4 to Solr 3.5 (or, even new Solr > >> version than 3.5, when available) in coming days. There are few questions > >> about this migration. > >> > >> > >> • I heard, index format is changed in this migration. So, does this require > >> me to reindex millions of data? > >> > >> • Are there any migration tool (or any other means?) available that would > >> convert old indexes (1.4) to new format (3.5)? > >> > >> • Consider this case. > >> http://myserver:8080/solr/mainindex/select/?q=solr&start=0&rows=10&shards=myserver:8080/solr/index1,myserver:8080/solr/mainindex,remoteserver:8080/solr/remotedata. > >> In this example, consider that 'myserver' has been upgraded with Solr 3.5, > >> but 'remoteserver' is still using Solr 1.4. The question is, would data > >> from remoteserver's Solr instance come/parsed fine or, would it cause > >> issues? If it results into issues, then of what type? how to resolve them? > >> Please suggest. > >> > >> • We are using various features of Solr like, searching, faceting, > >> spellcheck and highlighting. Will migrating from 1.4 to 3.5 cause any break > >> in functionality? is there anything changed in response XML format of here > >> mentioned features? > >> > >> Thanks in advance, > >> > >> Bhavnik > >> ** > >
