Hi Stephen, Nick from Websolr here. Indeed, we did have a bit of a hiccup earlier today. The number of indexes affected was relatively small, as it occurred on only one server. Folks that were affected would have been those who added the Websolr add-on between mid-December and mid-January.
Some more details, for those curious… It turns out that one of the other indexes on that server was improperly configured. Usually we can handle that case pretty gracefully, but this particular index exposed an edge case in Solr that we weren't previously aware of. Unfortunately, when we reloaded Solr this afternoon during the course of some normal maintenance, this particular configuration error prevented Solr from loading correctly. Hence the errors you experienced. We noticed the problem right away, and after a few minutes of troubleshooting were able to find and deploy a fix for the root cause. That fix has also since been deployed to all of our other servers to prevent this particular case from occurring again in the future. You mentioned some lingering issues… if anyone else experiences any persisting issues I encourage you to open a ticket at http://support.heroku.com/ or http://help.websolr.com/ with your WEBSOLR_URL so we can take a closer look. Also, the issue you mention with your number of documents being much larger than you expect sounds particularly puzzling… I'd definitely be curious to take a look at that, and can possibly help you migrate to a fresh index if that proves necessary. On Sun, Jan 30, 2011 at 4:57 PM, Stephen Cremin <[email protected]> wrote: > About two hours ago I got a message through from Exceptional that a search > failed with a "RSolr::RequestError". Sure enough, search was down on my > site. > > I checked the twitter feed of WebSolr: > http://twitter.com/websolr > > It didn't seem a coincidence that about the time search stopped working on > my site, they tweeted: > "A misconfiguration on one of our servers has a small number of indexes > down. We're working on it." > > WebSolr has been rock solid for me in recent months and it was the first > message on their Twitter feed since 22nd January. > > Their next Twitter message stated "It's fixed now". But even though my > account's status page indicated that my index "looks ok", I was still > getting errors. > > I was able to fix search on my site by going into the console and > reindexing the articles on my site: > heroku console > Sunspot.index!(Article.all) > > Stephen > > PS: According to my accounts page, the number of documents in my index has > somehow grown eight times after reindexing, but I'm not going to risk > hitting the "Destroy this index" button and rebuilding it again right at > this moment. > > -- > You received this message because you are subscribed to the Google Groups > "Heroku" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]<heroku%[email protected]> > . > For more options, visit this group at > http://groups.google.com/group/heroku?hl=en. > -- Nick Zadrozny http://websolr.com — hassle-free hosted search, powered by Apache Solr -- You received this message because you are subscribed to the Google Groups "Heroku" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/heroku?hl=en.
