I'll just add that upgrading need not be as frustrating / difficult as you might think given the following assumptions...
1. You have the resources to set up a new set of Servers or VM's with Solr 5 or 6 2. You have the data you need to re-index into the new servers. 3. You're running a load balancer that can easily point to the new servers... 4. You have access to your (Solr) config files and can pull out the pieces that are unique to you as "includes" -- thus bypassing most (and likely all) of the pain of figuring out how to change your configs to match a later version of Solr. In a sense, it won't matter how long it takes to index all the data into the new servers because your Prod is still running and you don't need to switch until everything is indexed, so if it takes a day or a week, or longer -- you'll be fine. If it's going to task your DB to heavily, you could consider using a recent backup of the DB - again on a separate VM or physical server. Naturally, you'd need to do a little testing first to ensure that everything worked well before switching over... One possibility is to capture a lot of Solr requests into something like Kafka - and then you'd be able to replay them against your new servers to verify that results are good (this step is a bit more complicated and might require you to touch code depending on how you're set up) Just throwing that out there since I've been through it recently -- in case it helps. If it doesn't help - feel free to ignore! On Tue, Sep 6, 2016 at 10:10 AM, Charlie Hull <char...@flax.co.uk> wrote: > On 06/09/2016 17:02, jake_4321 wrote: > >> Hi Alex, >> >> Thank you for responding. >> >> 4.0 - Version >> >> It can be any random Search query, but then the search facility will stop >> working >> >> > As Alex says, something will be causing the memory issues, although if > it's some kind of leak it may be cumulative - so memory will dribble away > over time and then whatever random query tips it over the edge will seem to > be causing the problem. > > You could probably fix this temporarily by giving the Solr process more > memory, but you should also try and find & fix the underlying problem - > although to be honest, this may not be worth it for a 4.0 system as you'll > be dealing with pretty old code (2012) - consider upgrading. > > Cheers > > Charlie > > > > >> >> >> >> -- >> View this message in context: http://lucene.472066.n3.nabble >> .com/Apache-SOLR-Search-Errors-tp4294814p4294821.html >> Sent from the Solr - User mailing list archive at Nabble.com. >> >> > > -- > Charlie Hull > Flax - Open Source Enterprise Search > > tel/fax: +44 (0)8700 118334 > mobile: +44 (0)7767 825828 > web: www.flax.co.uk >
