Board index MyODBC

MySQL inserts and disk full - how to handle gracefully?

MySQL inserts and disk full - how to handle gracefully?

Post by Andrew Braithwait » Sat, 02 Apr 2005 19:12:01



Hi All,

When you do a insert into a MySQL database and the disk is full, the
insert just hangs waiting for that table to become available.

This is fine for applications that care about data integrity.  In this
case I care more about availability and speed and would prefer it if the
inserts gracefully returned a nice error instead of waiting forever.

However - if the system is running a bit slow and the inserts are
queuing and taking a few seconds I wouldn't want them to fail in that
case.

Does anyone have any experience in this kind of "circumventing the
data-integrity protecting hang-on disk-full condition"?  I would love to
hear your thoughts and ideas..

Cheers for the help,

Andrew

SQL, Query

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql

 
 
 
Top

1. handling of quota-exceeded or end-of-disk-errors within mysql?

Hi,

we currently have a situation with our mysql-3.22.29 under
Solaris-2.7, where the databases itself are put on an NFS-mounted
filesystem. Yesterday we had a crash of the system and isamcheck
tried to recover some databases - but some people have reached or
already exceeded their quotas, therefore isamcheck can not recover
the files. The result are damaged indexes which causes crashes on
the mysqld, and tables which have only part of the filelenght it
should have.

has this behaviour changed in 3.23.*? Is it there handled gracefully?

Ciao, Hanno
--

| Eine gewerbliche Nutzung meiner Email-Adressen ist nicht gestattet! |

#"Ich bleibe lieber bei Doedelgate 0.03 beta, was auch ohne Konfiguration
# irgendwas tut, auch wenn ich noch nicht ganz verstanden habe, was das ist."
#       -- [nachgestellte Gatewaybetreiber Aussage] (Heiko Schlichting)

---------------------------------------------------------------------
Before posting, please check:
   http://www.mysql.com/manual.php   (the manual)
   http://lists.mysql.com/           (the list archive)



Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php

2. Problems with omniORB

3. handling of database size exceeding physical disk

4. Explorer.exe error log?

5. handling of database size exceeding physical disk space

6. C/C++ source codes of embedded applications

7. Problem shutting down MySQL Server gracefully

8. EPSON C60 INK REFILLS

9. InnoDB disk full problem

10. full disk: ERROR 1016: Can't open file

11. odbc.ini is deleted during high cpu load or disk full on sola

12. odbc.ini is deleted during high cpu load or disk full on solaris

13. innobase expects interactive input when disk is full


All times are UTC
Board index