June 20, 2013

Post: Recovery deleted ibdata1

ib_logfile1 (deleted) where 14101 is the PID of mysqld process. However, we can’t copy them back because at any given point of0.00 reads/s, 0 avg bytes/read, 0.00 writes/s, 0.00 fsyncs/s When all modified pages are flushed it is

Post: Recovery after DROP & CREATE

differentbytes) field data We know that sakila/actor is field #0, its length is 12 bytes. So, if we ever meet byteib_logfile1 sakila/actor sakila/actor 15 # ./s_indexes /var/lib/mysql/ib_logfile1 15 0-18 0-19 Now recovery of

Post: Shard-Query EC2 images available

size comparison, I used the du utility: InnoDB file size on disk: 42GB (with indexes) # du -sh * 203M ibdata1 128M ib_logfile0 128M ib_logfile1bytes of data. 64 bytes from shard20 (10.126.15.34): icmp_seq=1 ttl=61 time=0.637 ms … Note: There is

Post: Analyzing the distribution of InnoDB log file writes

ib_logfile1 The file descriptors are 8 and 9. We’ll need to capture writes to both of0, the distribution may be quite different — the writes might accumulate and become much larger. What happens if the log buffer is