Accessing Drupal if Solr Inaccessible [#1673654]

This may not be a Sarnia issue. So I apologize in advance if it isn't. But recently the solr server became inaccessible. Once this happened, I was unable to access Drupal (when attempting to login). I consistently get this error on a white error page:

Apache_Solr_HttpTransportException: '-111' Status: Unknown Status in Apache_Solr_Service->_sendRawGet() (line 338 of /opt/vtls/lampstack/apache2/htdocs/drupal/sites/all/libraries/SolrPhpClient/Apache/Solr/Service.php).

Same thing happens if I try to do anything with Drush (clear cache, disable modules, etc). Any ideas as to how I may get around this error? I need to change the solr address... but ultimately, I'd like to figure out how to prevent such an error in the future that would only disable solr searching and not affect the entire Drupal instance.

Thanks,
Tony

Comment	File	Size	Author
#2	sarnia-solr-connection-1673654-2.patch	959 bytes	larowlan
#2

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

becw CreditAttribution: becw commented 2 August 2012 at 16:01

Status:

Active

» Needs work

Interesting. From the exception, it seems like this is rooted in Search API Solr. If the Solr server isn't available, it definitely shouldn't take down the site, preferably shouldn't show exceptions to end users, and hopefully won't try to hit Solr on every page view until it comes back up.

It's possible that it's Sarnia that is abusing the Solr connection; we should look into how Sarnia behaves with a missing Solr server vs. how Search API Solr behaves, and whether Sarnia is doing too much here.

This has actually been reported in the Search API Solr issue queue, but the issue was about the error messages rather than the behavior: #1340244: Friendlier error exception notices.