Usually after a sapi-i with a big dataset.. I get this error.

PDOStatement::execute(): MySQL server has gone away Statement.php:59   [warning]
PDOStatement::execute(): Error reading result set's header             [warning]
Statement.php:59
Drupal\Core\Database\DatabaseExceptionWrapper: SQLSTATE[HY000]:          [error]
General error: 2006 MySQL server has gone away: CREATE TABLE
{cache_bootstrap} (

Comments

chriscalip created an issue. See original summary.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Status: Active » Postponed (maintainer needs more info)

Sorry, not sure what to do about that. Do you have any suggestions?
It seems the load is simply too much for the MySQL server. So, probably just don’t index too many items at once (even with a batch operation, as we’re using)?
Are the items at least indexed OK?
Are you using the database backend?

chriscalip’s picture

chriscalip commented

@drunken_monkey
Indeed the dataset is huge.
Using algolia search as the search_api backend
All the items are indexed.
It looks like a post import that keeps crashing.

drunken monkey’s picture

drunken monkey
he/him
Primary language German
Location Vienna, Austria
commented
Category: Bug report » Support request
Status: Postponed (maintainer needs more info) » Fixed

Then yes, unless you can point to some bug in the Search API that’s causing this, or some specific thing which we could improve, I fear I can only give you the advice of not indexing too much at once and waiting for the MySQL server to “calm down” in between.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.

kwiechmann’s picture

kwiechmann commented

Experiencing the what appears to be the same error message on a current project. Wondering if there is any additional information? Looking at Comment #4 but it seems very kludgey.

AdvThanksance!!!