My solr Update extract handler stopped working after upgrading from 4.0 to 4.2
When I upgraded from solr 4.0 to 4.2 suddenly all the file uploads using /update/extract stopped working. I noticed a class was missing.
I've solved this by making by changing solrconfig(from 4.2) with the changes I had in 4.0.
Because of al these problems I'm wondering whats the best way to upgrade from Solr 4.0 to 4.2? (or any other version)
I just copied the new war,dist folder and contrib folder and tought it would be fine but it sure isn't. I know re-indexing is recommended.
Standalone - Standalone mode is the commonly recommended setup for Production. Solr is executed in its own JVM which makes it much easier to monitor reliability and scalability. Production environment should always use a Solr cluster, which runs multiple Solr instances running in standalone mode.
Solr and SolrCloud are not separate things; Solr is the application while SolrCloud is a mode of running Solr. The alternative to running Solr in SolrCloud mode is running it in standalone mode.
SolrCloud is flexible distributed search and indexing, without a master node to allocate nodes, shards and replicas. Instead, Solr uses ZooKeeper to manage these locations, depending on configuration files and schemas. Queries and updates can be sent to any server.
Typically when I upgrade between Solr versions, I follow the steps outlined below...
solrconfig.xml
and schema.xml
in the /example/solr/collection1/conf
folder with the same files from the version of Solr from which I am attempting to upgrade (Solr 4.0 in your case). I use a tool like DiffMerge or something similar to help highlight the differences.Yes, I agree that re-indexing is best when you can, as the underlying version of Lucene is changing as well and a re-index will be required to leverage any new features or improvements.
Hope this helps.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With