Thanks John... yes that was the first idea came to our mind, but it will require doubling our servers (in replica data centers as well etc), definitely we can't afford the cost.
We have thought of first establishing a small pool of 'hot' servers and use them to take incoming new index data using upgraded solr version (a relative much smaller resources pool), meanwhile take one exist server (and its replicas as well) at one time to upgrade one by one. Although most (99%) index will happen at the small hot servers pool, but there are still some of the updates to the 'cold' servers at all time. We will also need to introduce a write lock down on the impacted servers... with one server at a time, the scope of impact will be reduced to its minimum... I am pretty sure we must not be the only one that has to face the re-index issue with large data set... am I correct? If there is a better approach, please share... thanks a lot! Renee -- View this message in context: http://lucene.472066.n3.nabble.com/solr-5-leaving-tomcat-will-I-be-the-only-one-fearing-about-this-tp4300065p4300550.html Sent from the Solr - User mailing list archive at Nabble.com.
