- Issue created by @josephgut
- 🇩🇪Germany gbyte Berlin
We usually don't get these kind of reports which indicates the module is quite scalable.
I have even updated my AWS EC2 server from a T3 Small (2G RAM) to T3 Medium (4G RAM) and it did help reduce the errors a bit, but they're still happening. I am using a T3 Small for the AWS RDS DB (perhaps 2G isn't enough for the DB? to use this module?).
4GB RAM isn't much but it should be enough. Maybe PHP is running out of memory and so the database query does not finish? How much memory is PHP allowed to use in your case? You can check it by visiting /admin/reports/status
7. Maximum links in a sitemap: 20000 (tried lower and higher numbers too)
Try to keep this low - for the sake of testing maybe 200
8. Sitemap generation max duration: 15 (have tried 30, 60, 200 - still get error)
That might be a problem, you want a lower value to save memory. Try 5 for the sake of the test and go from there.
There are also mysql configuration options that you could look at, but I personally never had to change those... Example:
[mysqld] wait_timeout max_allowed_packet
Maybe there is some strange query error because of a broken data set? Can you try and regenerate the sitemap with different content?
You could also look at mysql logs.