Last modified: 2014-02-14 20:07:15 UTC
Currently Solr 3.6.0 is being used. Please update to 3.6.2. I think this is about the package "solr-jetty", as is specified in puppet's modules/solr/manifests/init.pp.
> Please update to 3.6.2. Reasons would be good. Not sure if we use Ubuntu's default packages, in case we do I cannot see it listed for Ubuntu Precise in the package list. http://packages.ubuntu.com/source/quantal/lucene-solr (3.6.1) http://packages.ubuntu.com/source/saucy/lucene-solr (3.6.2)
Siebrand: Could you provide some specific features / bugfixes / reasons for backporting?
Solr 3.6.1 Release Highlights: * The concurrency of MMapDirectory was improved, which caused a performance regression in comparison to Solr 3.5.0. This affected users with 64bit platforms (Linux, Solaris, Windows) or those explicitely using MMapDirectoryFactory. * ReplicationHandler "maxNumberOfBackups" was fixed to work if backups are triggered on commit. * Charset problems were fixed with HttpSolrServer, caused by an upgrade to a new Commons HttpClient version in 3.6.0. * Grouping was fixed to return correct count when not all shards are queried in the second pass. Solr no longer throws Exception when using result grouping with main=true and using wt=javabin. * Config file replication was made less error prone. * Data Import Handler threading fixes. * Various minor bugs were fixed. Source: http://mail-archives.us.apache.org/mod_mbox/www-announce/201207.mbox/%3C010901cd6811$22088990$66199cb0$@apache.org%3E Solr 3.6.2 Release Highlights: * Fixed ConcurrentModificationException during highlighting, if all fields were requested. * Fixed edismax queryparser to apply minShouldMatch to implicit boolean queries. * Several bugfixes to the DataImportHandler. * Bug fixes from Apache Lucene 3.6.2. Source: http://mail-archives.apache.org/mod_mbox/www-announce/201212.mbox/%3CCAOdYfZW9cTKvrPcp3s7z1w-yPEAALzth62nsG_pxk_GpSAAufQ@mail.gmail.com%3E Fixes from Apache Lucene 3.6.2: * Fixed ArrayIndexOutOfBoundsException when the in-memory terms index requires more than 2.1GB of RAM (billions of terms). * Fixed a bug in contrib/queryparser's parsing of boolean queries. * Fixed BooleanScorer2 to return the correct freq() when using the scorer visitor API. * Fixed IndexWriter RAM accounting bug that would cause it to flush too early when using many different field names. * Several other minor bugfixes: scoring bugs when using a custom coord(), a rare IndexWriter thread-safety issue, and fixes to the faceting and highlighting modules. Source: http://mail-archives.apache.org/mod_mbox/www-announce/201212.mbox/%3CCAOdYfZVtM21W=fKe8D82fCpKhrMEBBo7QjjmgZrp-tMv7stQhA@mail.gmail.com%3E
Now the WMF infrastructure seems to be moving in the direction of Elasticsearch - shouldn't we all convert from Solr instead of upgrading it?
(In reply to comment #4) > Now the WMF infrastructure seems to be moving in the direction of > Elasticsearch > - shouldn't we all convert from Solr instead of upgrading it? That's bug 52993. In general, let me remind that perfection is the enemy of good. :)
