Re: Limitation of DRBD For MySQL
On 6/18/07, Eric Bergen [EMAIL PROTECTED] wrote: Hi, You have hit most of the reasons. One other important one is that if a table or filesystem is corrupted that corruption is propagated over to the drbd slave. My opinion and several other reasons can be found here: http://ebergen.net/wordpress/2007/04/02/drbd-in-the-real-world/ Thanks, I really appreciate it. -- Regards, Mohd Irwan Jamaluddin Web: http://www.irwan.name/ Blog: http://blog.irwan.name/ -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Re: Limitation of DRBD For MySQL
Hi, You have hit most of the reasons. One other important one is that if a table or filesystem is corrupted that corruption is propagated over to the drbd slave. My opinion and several other reasons can be found here: http://ebergen.net/wordpress/2007/04/02/drbd-in-the-real-world/ -Eric On 6/17/07, Mohd Irwan Jamaluddin [EMAIL PROTECTED] wrote: Good day, Someone gives me several limitations of DRBD For MySQL? Here is the list, 1. Idle resource – secondary host sits idle, wasted investment 2. Failover is not instant, nor transparent -Cold standby failover 3. Recovery requires time to start / recover database 4. Recovery process can fail – requires reload 5. Requires database journal capability -MySQL MyISAM does not work 6. Operation not continuous: planned downtime required -Active-passive does not cover DB maintenance -Anything that requires mounted disk 7. Does not address scaling or performance 8. OS Limitations – Some only run on Linux May someone elaborate or disprove those points? Thanks. -- Regards, Mohd Irwan Jamaluddin Web: http://www.irwan.name/ Blog: http://blog.irwan.name/ -- Eric Bergen [EMAIL PROTECTED] http://www.provenscaling.com -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe:http://lists.mysql.com/[EMAIL PROTECTED]
Limitation of DRBD For MySQL
Good day, Someone gives me several limitations of DRBD For MySQL? Here is the list, 1. Idle resource – secondary host sits idle, wasted investment 2. Failover is not instant, nor transparent -Cold standby failover 3. Recovery requires time to start / recover database 4. Recovery process can fail – requires reload 5. Requires database journal capability -MySQL MyISAM does not work 6. Operation not continuous: planned downtime required -Active-passive does not cover DB maintenance -Anything that requires mounted disk 7. Does not address scaling or performance 8. OS Limitations – Some only run on Linux May someone elaborate or disprove those points? Thanks. -- Regards, Mohd Irwan Jamaluddin Web: http://www.irwan.name/ Blog: http://blog.irwan.name/
