-
Notifications
You must be signed in to change notification settings - Fork 74
Upgrade to Solr 4.4.0 #197
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Make sure to delete the solr dir and build dir generated at compile time.
Upgrade to the custom Yokozuna build of Solr 4.4.0. * Modify the `solr.xml` file to use the new format. See http://wiki.apache.org/solr/Solr.xml%204.4%20and%20beyond * Fix `grab-solr.sh` to not fail on mkdir.
* Use set -e so that script fails if patches fail to apply * Add some additional checks for robustness
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🐟
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Dat set -e.
|
Here are the benchmark results. Numbers are very close. The interesting thing to note is that when I first ran the benchmark query throughput had dropped to 670 ops/s or 44% of baseline. I had forgotten to update the solr dist search patch in https://issues.apache.org/jira/browse/SOLR-4509 Indexing
Query
Query Without Dist Search Patch
|
|
Tests are consistent with current 2.0 testing, i.e., all pass but |
|
Same deal with me. yz_rs_migration was a no go. |
|
Yep, that test is still broken. Needs this update plus other fixes. |
This makes the necessary requirements to upgrade to Solr 4.4.0. A simple benchmark shows same performance before/after. I'll post graphs tomorrow.
Solr 4.4.0 also enables us to try out the new "schemaless" mode but that should be it's own PR. Furthermore, 4.5.0 should be coming out any day now. That upgrade should be done for the 0.11.0 release. But I wanted to update to 4.4.0 first to make that transition easier.