Hi John , Shawn Thanks for replying to my query . Really appreciate your responses
Ideally I’d like to do node by node rolling upgrade from 4.4 to 5.5 But gave this approach of rolling upgrade because I faced issue with SolrJ 4.4 client connecting with 5.5 cluster or 5.5 solar client connecting with 4.4 cluster. I am fine with stopping whole cluster and upgrade all nodes to 5.5. What I don’t want to do recreate complete index for all clients from source system. At least I’d like to avoid recreate index from source as that will be really time consuming process for us. This is what I have done 1. Stop all nodes and zookeeper 2. Updated solr 4.4 to 5.5 on all cluster nodes 3. Deleted zookeeper data 4. Modify solr.xml, solrconfig.xml, created core.properties as per 5.5 changes 5. Boot strap from existing solr home using this command ./solr-5.5.0/server/scripts/cloud-scripts/zkcli.sh -z <zookeepr server and port> -cmd bootstrap -solrhome /home/solr/solrcloud-shard1 -d <path to sole con directory> -n <cofig name> -c <collection name> 6. Start zookeeper 7. start all solr nodes all nodes comes up correctly. I can query data fro solr ui as well as from our application using solrJ client upgraded to 5.5 libs What I see that clusterstatus.json and /collections/<collectionName> shows implicit router not compositId router When I update document, it doesnt go to right shard but different shard Just for trying purpose, I manually updated clusterstatus.json and /collections/<CollectionName> with compositeId router and shards keys after stopping cluster and zookeeper and restar after update of json files Based on your reply, I think suggested steps are ( please confirm if these are appropriate) 1. Stop all nodes and zookeeper 2. Updated solr 4.4 to 5.5 on all cluster nodes 3. Deleted zookeeper data 4. Modify solr.xml, solrconfig.xml, created core.properties as per 5.5 changes 5. start zookeeper 5. upload config to zookeeper 6. Create collection using rest api 7. start cluster 8. copy collection data from 4.5 to solr 5.5 data directory If you can share upgrade step/process document, that will be great Thanks Anuj On Apr 6, 2016, at 7:58 AM, John Bickerstaff <j...@johnbickerstaff.com> wrote: I recently upgraded from 4.x to 5.5 -- it was a pain to figure it out, but it turns out to be fairly straightforward... Caveat: Because I run all my data into Kafka first, I was able to easily re-create my collections by running a microservice that pulls from Kafka and dumps into Solr. I have a rough draft document for how to "upgrade by replacement" in this way - basically, throw away the older Solr, build a new /chroot in Zookeeper and issue a few command line commands to upload configs (from the 4.x version) and create new collections in the 5.x version. If this is what you mean by "bootstrap" (Upgrade to 5.x but use your index/collection/core from a previous version) then perhaps I can help. There were instructions on the Solr wiki for the differences between 4.x and 5.x... But before I go into a lot more detail, please drop us a line and let me know if that's what you need... For reference you can look at this, but I have more refined instructions now: http://stackoverflow.com/questions/34909909/how-to-correctly-add-additional-solr-5-vm-nodes-to-solr-cloud?rq=1 On Wed, Apr 6, 2016 at 7:01 AM, Shawn Heisey <apa...@elyograg.org> wrote: On 4/5/2016 3:08 PM, Anuj Lal wrote: I am new to solr. Need some advice from more experienced solr team members I am upgrading 4.4 solr cluster to 5.5 One of the step I am doing for upgrade is to bootstrap from existing 4.4 solr home ( after upgrading solr installation to 5.5) We'll need a lot more detail about *exactly* what "bootstrap" means here. The fact that you chose the word "bootstrap" to describe your process sets off a red flag in my mind, and might mean that you're doing this upgrade in a way that won't work like you're expecting it to. One particular question I'd like to have answered: Are you upgrading each server in place using the exact same zkHost string as the 4.4 install was using, or are you trying to build up a new ZK chroot/database using the existing Solr home? I have not actually performed one of these SolrCloud upgrades, but I would expect that if you don't connect to the existing zookeeper database, it would probably behave exactly like you've described. If I'm completely wrong about how this should be done, somebody please let me know. Going from 4.4 to 5.5 is a significant upgrade (including one major release, 10 minor releases, and 10 bugfix releases) and you might find that the two versions won't coexist very well. The devs do try to make different versions compatible, but SolrCloud is evolving at an extremely rapid pace, so this cannot be guaranteed when the version difference is so large. Assuming I have a correct mental picture of how you got to where you are, there might be some things you could do to get it back on track, but that would require significant manual fiddling, and no guarantee of success. Thanks, Shawn
