Come together with the global Drupal community in Rotterdam, 28 Sept – 1 Oct 2026. Sessions, contribution, connection, and Early Bird savings until 8 June.It's my understanding that if a server is disabled, then queries will no longer be sent to it. I'm having a problem that when a server is disabled programatically. (or via the database record), entity changes that fire of indexing still happen. This is unacceptable because I'm trying to disable the server so that people developing will not screw with the production server.
My install script looks something like this
drush sqlq "UPDATE search_api_server SET enabled = 0 WHERE machine_name = 'acquia_search_server'"
drush updb -y
The updates delete and create nodes. The index that is still pointing at the server is connecting to the server and updating it.
| Comment | File | Size | Author |
|---|---|---|---|
| #1 | search_api-no_indexing_for_disabled_server-2505421-1.patch | 2.04 KB | generalredneck |
Comments
Comment #1
generalredneckThis puts some checks in place that prevents query going to disable servers.
Comment #2
drunken monkeySolution: Don't change data in the database if you don't know what you are doing!
If you'd use the proper code to disable the server, all indexes on it would be automatically removed from it and disabled, eliminating this problem.