Changes between Version 20 and Version 21 of PS1_IPP_Czarlog_20141208

Timestamp:

Dec 9, 2014, 1:07:57 PM (12 years ago)

Author:

Mark Huber

Comment:

--

PS1_IPP_Czarlog_20141208

@@ -28 +28 @@
  * 07:45 EAM : processing has been limping along, with a number of the 'table full' errors.  there is enough room on the disk after Serge purged the binary logs, so that is not the cause.  the tables are big, but not approaching the InnoDB 64 TB max values.  The load on the machine (ippdb00) is modest (3-4).  I am guessing that a restart of mysql might clear out something which is cached?
  * 08:10 EAM : more research has revealed the likely cause: the number of concurrent transactions was too large (the full disk probably also triggered this).  I turned down the number of nodes doing cleanup and this seems to be making things better (lower error rate).  the following mysql bug report is relevant (and points out that 5.5.xx has bumped the transaction limit): http://bugs.mysql.com/bug.php?id=26590
-  * [wiki:PS1_IPP_Czarlog_20141201#Saturday:2014.12.06] -- when looking at the logs on saturday after powerup seems like we have been hitting this since mid-october
+  * [wiki:PS1_IPP_Czarlog_20141201#Saturday:2014.12.06] -- when looking at the logs on saturday after powerup seems like we have been hitting this harder since mid-october
  * 08:15 EAM : addendum: this is probably not as critical, but we may want to bump the ibdata file.  this is from the mysql manual (http://dev.mysql.com/doc/refman/5.0/en/innodb-data-log-reconfiguration.html)