On 07/04/2014 16:45, Steve Wilson wrote:
> A quick read at
> http://dev.mysql.com/doc/refman/4.1/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit
> suggests there's a possibility of losing 1s worth of data. I'm not sure
> if we'd still have a problem with this now we've moved page ca
A quick read at
http://dev.mysql.com/doc/refman/4.1/en/innodb-parameters.html#sysvar_innodb_flush_log_at_trx_commit
[2]
suggests there's a possibility of losing 1s worth of data. I'm not sure
if we'd still have a problem with this now we've moved page caching to
memcache as that was causing a lo
Thanks Steve for your update. We are using separate mysql server and in
this innodb_flush_log_at_trx_commit = 1. This site is running money
transactions applications so is it safe to change this option.
Also to this mysql server other servers with default nginx and PHP5-fpm
configuration is con
I've just done a drupal7 site under nginx+php-fpm on debian.
One thing I noticed was that the php process wasn't closing fast enough,
this was tracked down to an issue with mysql. Connections were sitting
idle for a long time which basically exhausted the fpm workers on both
the web servers.
We are facing a strange issue on our servers. We have servers with 1GB RAM
and some drupal sites are running on it.
Generally all sites are loading fine but sometimes we are unable to access
any sites. After waiting for 10mts we are getting a 502 gateway timeout
error. In middle when we restart
