replication for BDB tables
Hi, With all the recent talk about replication, just wondering if there are any others out there who have experience replicating BDB tables? My experience so far has been that the slave instance of MySQL has been crashing once in a while, when applying perfectly legitimate DELETE queries on the replicated BDB tables. MySQL then restarts after the crash, but not without spewing out various BDB Log Sequence errors etc in the log when trying to recover. On restarting, the same query causes an error on the affected table again, and the only way to get things going again is to convert BDB - MyISAM - BDB, then SLAVE START. This of course does not bode well on a production system where the slave acts as a hot backup just in case :) Just sharing my experience so far :) Anyone else got anything to share? Some other questions : 1. Does anyone know the behaviour of BDB recovery for such cases i.e. table crashes, log sequence errors etc? 2. What happens to BDB tables on shutdown/startup i.e. is the transaction log flushed etc? Any comments welcome! Thanks. Cheers, Geoffrey __ Geoffrey Soh, Software Architect Ufinity - http://www.ufinity.com Leading Enterprise Access Management Software! 9 Scotts Road, Pacific Plaza, #06-01, Singapore 228210 Tel : +65 830-0341 Fax : +65 737-0213 __ - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
Re: replication for BDB tables
On Fri, Jan 25, 2002 at 04:15:18PM +0800, Geoffrey Soh wrote: Hi, My experience so far has been that the slave instance of MySQL has been crashing once in a while, when applying perfectly legitimate DELETE queries on the replicated BDB tables. That's a bad sign. MySQL then restarts after the crash, but not without spewing out various BDB Log Sequence errors etc in the log when trying to recover. On restarting, the same query causes an error on the affected table again, and the only way to get things going again is to convert BDB - MyISAM - BDB, then SLAVE START. This of course does not bode well on a production system where the slave acts as a hot backup just in case :) Next time it happens, make a copy of the bad table and the query that caused the problem. Send it to the MySQL folks so they can track down (and fix) the problem. This shouldn't be happening at all. Jeremy -- Jeremy D. Zawodny, [EMAIL PROTECTED] Technical Yahoo - Yahoo Finance Desk: (408) 349-7878 Fax: (408) 349-5454 Cell: (408) 685-5936 MySQL 3.23.41-max: up 22 days, processed 514,708,248 queries (266/sec. avg) - Before posting, please check: http://www.mysql.com/manual.php (the manual) http://lists.mysql.com/ (the list archive) To request this thread, e-mail [EMAIL PROTECTED] To unsubscribe, e-mail [EMAIL PROTECTED] Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
