[DRBD-user] drbd+mysql+innodb

Robinson, Eric eric.robinson at psmnv.com
Thu Jun 13 16:23:55 CEST 2013

Note: "permalinks" may not be as permanent as we would like,
direct links of old sources may well be a few messages off.

> you've been doing this with MyISAM? You got lucky then. Your 
> work loads are likely not very write heavy.

They are about 80% read, 20% write.

500 instances of MySQL running for 7 years works out to 3500 years of MySQL run-time. That's a pretty fair amount of luck. Maybe MyISAM is not as bad as some people suggest?

> InnoDB streamlines its disk writes quite a bit. Writes get 
> commited to logfiles first, so the tablespace needs not be 
> rebuilt after every single transactional commit etc. So I 
> guess as long as the database is running, there is room for 
> fuzziness among in-memory representation(s) of the dataset 
> and what's on disk.
> Of course, you do gain the ability to take a crash-complete 
> image of the mysql data, e.g. by severing drbd replication 
> and reading from the secondary machine.
> HTH,
> Felix

Every little bit helps. 


Disclaimer - June 13, 2013 
This email and any files transmitted with it are confidential and intended solely for 'Felix Frank','Paul Walsh',drbd-user at lists.linbit.com. If you are not the named addressee you should not disseminate, distribute, copy or alter this email. Any views or opinions presented in this email are solely those of the author and might not represent those of Physicians' Managed Care or Physician Select Management. Warning: Although Physicians' Managed Care or Physician Select Management has taken reasonable precautions to ensure no viruses are present in this email, the company cannot accept responsibility for any loss or damage arising from the use of this email or attachments. 
This disclaimer was added by Policy Patrol: http://www.policypatrol.com/

More information about the drbd-user mailing list