Acquia Search disconnected after cron run - incorrect URL [#2569759]

On one of our sites (hosted on Acquia Cloud), the Solr Search disconnects after cron. It doesn't happen on every cron run, so it's a bit difficult to replicate.

Acquia Solr - disconnected after cron

Connection to Solr is done via settings.php variable:

$conf['apachesolr_default_environment'] = 'acquia_search_server_1';

After the cron, incorrect URL to Solr is set:

wrong URL to Solr

Re-saving the Solr settings screen resolves the issue.

UPDATE #1

I wrote a short module to work around the problem. It's probably not the solution - it should be fixed in the module itself - but it might help someone else. Code can be found here: Acquia Search Reconnect.

Possibly related issues:

Comment	File	Size	Author
	acquia-solr-url.png	123.1 KB	david.lukac
	acquia-solr-cron.png	105.52 KB	david.lukac

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

Comment #1

16 September 2015 at 19:31

david.lukac created an issue. See original summary.

Comment #2

david.lukac CreditAttribution: david.lukac as a volunteer and at i-KOS commented 16 September 2015 at 19:35

Issue summary:

View changes

Comment #3

david.lukac CreditAttribution: david.lukac as a volunteer and at i-KOS commented 16 September 2015 at 20:13

Issue summary:

View changes

Comment #4

david.lukac CreditAttribution: david.lukac as a volunteer and at i-KOS commented 17 September 2015 at 06:41

The issue has been also raised with Acquia support.

Comment #5

david.lukac CreditAttribution: david.lukac as a volunteer commented 17 September 2015 at 13:39

Update: the issue seems to be caused by exporting Solr environment settings (which contains the URL as well). We originally didn't have that exported, because Acquia sets all those values automatically, but it probably sneaked in when we added list of content types which should be indexed to Feature export.

The incriminating code in the feature:

solr_search.apachesolr_environments.inc:15:  $environment->env_id = 'acquia_search_server_1';
solr_search.apachesolr_environments.inc:17:  $environment->url = 'http://search.acquia.com/solr/';

Comment #6

Stanislav Mixnovich CreditAttribution: Stanislav Mixnovich commented 27 November 2015 at 14:09

@david.lukac This problem is still reproduced ?
if yes, then try updating Acquia Search Multiple Indexes module https://www.drupal.org/project/acquia_search_multi_subs
I think that the problem in this module.

Also see this issue:
https://www.drupal.org/node/2365243

Comment #7

david.lukac CreditAttribution: david.lukac as a volunteer commented 28 November 2015 at 16:51

Priority:	Normal	» Minor
Related issues:		+#2365243: Periodic issues with getting subscription data

Hi Stan, partially yes. We do use the multi-index module, but for some reason Solr still says that it's disconnected on cron run and then reconnects. Another issue with multi-index module is that when exported into a Feature, specific core values are exported, which is than messed up (overridden) when deployed to different environments (I'll update with specific error messages and values - currently @ DrupalCamp Vienna ;-).

On the other hand I haven't encountered any issues with subscription settings as described in referenced issue.
Br, D