On 8/14/2013 8:04 AM, Tor Egil wrote: > This is from the leader log. (There are other statements inbetween, but I > think they are irrelevant). First of all it reads the zookeeper state. This > happens now and then. Then I guess the replica says "Hey, I'm alive, please > start the recover process": > > > From the replica log, which tries to recover. For some reason I get the > "read timed out", as if solr was dead.. (but it clearly isnt). Maybe I could > turn on debug logging to view the actual URL for the query? > Also, I can see the replica telling zookeeper its alive and recovering. > > > I left this looping for a while in case of some bad synchronizations, but it > never recovers. > > The name of the core "swap" is used because I would like to upload new > configs to the swap core, and then do an actual swap when the core is up and > running with new data....
I'm not sure what happens if you swap cores in a SolrCloud environment. It's possible that this kind of swapping could lead to a very unstable system. FYI: Whatever Nabble forum feature you are using to change the font does not translate over to the mailing list. The altered text simply gets deleted. What you see above is what list subscribers (including Mark and I) can see without visiting the Nabble website. The canonical copy of this discussion is the mailing list and not Nabble. Many experienced users read this in a text email program that doesn't have any graphical browser capability, so even though there is a link at the bottom of your messages to see the topic on Nabble, it isn't useful for those users. Thanks, Shawn
