Problem/Motivation

The project documentation states that v4 of this module is required for connecting to Acquia Search.

However, when using the connector, our site was being pointed to a different application on our account, which meant that the search server configuration was not able to access the expected index IDs.

The only way we have been able to access the Solr index has been to disable the Connector, and provide our subscription identifier, key, uuid, and hostname manually.

We have multiple other applications that are able to use Connector and Search together, but they are using different versions of the modules.

Steps to reproduce

Failing state:
Acquia Connector 4.0.0
Acquia Search 3.0.7

Working state:
Acquia Connector 3.0.4
Acquia Search 3.0.5

Comments

akalata created an issue. See original summary.

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented
Status: Active » Postponed (maintainer needs more info)

Pushing for more info, I believe we have an internal ticket about this and it's not pointing to the wrong account, but the output could be improved.

danflanagan8’s picture

danflanagan8
Primary language English
Location St. Louis, US
commented

I'm working on a project that may be having this same issue. We are using acquia_connector v4.0.0 and acquia_search v3.0.9.

What happens with our sites is that search gets broken during deployments. We resave the acquia_search_server config manually through the UI after deployments in order to reconnect successfully.

I was under the impression that acquia_connector was supposed to make this happen automatically, but my understanding may be incorrect magical thinking.

Mention of an "internal issue" came up in an exchange with Acquia support. This looked like maybe the closest thing in the public issue queue.

mglaman’s picture

mglaman
Primary language English
Location WI, USA
commented

What happens with our sites is that search gets broken during deployments. We resave the acquia_search_server config manually through the UI after deployments in order to reconnect successfully.

That's what https://git.drupalcode.org/project/acquia_search/-/commit/0d371a697662e2... should have fixed, but you're saying you still need to re-save the config entity in a new environment? This was released in 3.0.8 and 3.0.9

danflanagan8’s picture

danflanagan8
Primary language English
Location St. Louis, US
commented

Hi, @mglaman!

I think the commit/release you referenced fixed an issue we were having where our solr connection was failing entirely, even after re-saving. Now we can connect to solr successfully, but it still requires a re-save after deployments.

[a few hours pass...]

We just tried something new, though, that seems to have fixed our problem. Somehow the connector_config part of the search_api.server.acquia_search_server ended up with several properties set that look like they aren't supposed to be there. I'm not totally sure what properties are supposed to be defined (there's no schema: #3176635: search_api.server.acquia_search_solr_search_api_solr_server:backend_config.connector_config missing schema). But comparing our active config with the default config from the acquia_search module, the following properties were present on our config but not the default config:

  1. identifier
  2. api_key
  3. uuid
  4. api_host
  5. skip_schema_check
  6. host
  7. port
  8. path
  9. core
  10. jts
  11. solr_install_dir
  12. key
  13. overidden_by_acquia_search (the value was 1)

I deleted all those properties from the configuration. After deploying that change, our sites appear to be connecting correctly without having to re-save in the UI.

So it looks like my problem was unrelated to this issue.