Mitch Pronschinske is a Senior Content Analyst at DZone. That means he writes and searches for the finest developer content in the land so that you don't have to. He often eats peanut butter and bananas, likes to make his own ringtones, enjoys card and board games, and is married to an underwear model. Mitch is a DZone Zone Leader and has posted 2573 posts at DZone. You can read more from them at their website. View Full User Profile

Solr Migration: 1.4 to 3.5

02.13.2012
| 4849 views |
  • submit to reddit
When Solr versioning changed to align with Lucene and it hit 3.x, the implications were major - not only in terms of the migration differences that you need to be aware of, but also in terms of the benefits that make the migration totally worth it.

It's important to understand that you don't simply install a new version and do a little dance, there are a few things that you need to be aware of, and for that process Nick Veenhof has some advice on his blog:

If you want to migrate to Solr 3.5 coming from Solr 1.4 with low risk of changes you should keep using the LogByteMergePolicy with a mergefactor of 4 (Default in the Drupal configs).
However, the TieredMergePolicy is interesting when understood correctly. I'd love some more comments on that topic from people that know more about it.  --Nick Veenhof

For Nick, the migration was a learning experience from which he also realized the massive performance benefits that Solr 3.5 brought.

Check out his blog post for the steps he took during migration and the graphical data he put together to show off his performance gains.

Also check out these docs from Apache for some background:

LogByteSizeMergePolicy
LogDocMergePolicy
TieredMergePolicy

Source:  http://www.nickveenhof.be/blog/upgrading-apache-solr-14-35-and-its-implications
Tags: