The table ‘table_ Name 'is full exception troubleshooting and solution

background

The project has been put into operation for one and a half years , During this period, some changes have been made due to the modification of requirements , However, the basic ordering function has not been changed since it was launched , And the project has not been updated in the last half year , Stable operation all the time, including this ordering function , But the day before yesterday, the order failed , I didn't pay much attention at first , Because this ordering function will call three-party services to do pre operations ( Third party services limit orders to one per user per day , Only after the three-party service is successful can the warehousing operation be performed ), And the message that prompts the user is to place repeated orders , Therefore, the prompt that the user fails to place an order and places an order repeatedly is a normal phenomenon ; However, the subsequent orders on that day are repeated orders that fail ; I feel wrong at this time . Hurry to check the log information of the service , The log information is as follows ：

Seeing the online service error log can explain why all orders fail , First of all, no matter what exception information the service throws , Will be caught by the global exception handler , Package into unified exception information and return , When the user places an order for the first time that day , Successfully placed the order in the third-party service , But our own service is abnormal , The front end displays an error message , The user thinks the order failed , Initiate the second order placing operation ; At this point, calling the third-party service will prompt you to place repeated orders , Our service will return the prompt of repeated orders to the front end , Cause the false appearance of repeated order prompt, so that we think it is a normal prompt without paying too much attention .

solve

According to the exception prompt is “The table ‘xxx_order’ is full”, It obviously means order The watch is full , In combination with the current scenario, when inserting an order order The error reported , So that's to say order Insufficient table space , Cause insertion failure ; There are two kinds of situations ：
First of all ： The amount of data in this table exceeds the maximum limit
If used MyISAM Storage engine ,MAX_ROWS Parameter limits the number of data entries per table , You can check whether the number of data entries in the corresponding table reaches this value , When the value is reached, the value setting can be increased ;innodb The storage engine does not MAX_ROWS Parameters .
about innodb For the storage engine, if page size by 16KB, Then the maximum size of the table is 64TB; This size is almost impossible to achieve , If the data volume is too large, the operation of database and table shall be considered .

second ： The server disk is full
The problem I encountered here is that the server disk is full , If the server disk is full , This will cause all tables to fail to insert , How to check it out ：
a、 adopt df -h Instructions , Check the server disk usage , If use One column adds up to 100% The disk is used up , The following figure shows the situation after deleting the file , So the disk occupation is not very high .

b、 When you see that the disk usage is very high , Start from the root directory and find out which directory takes up the most disk space , Instructions ：du -h --max-depth=1, You can see usr、root、var The three directories occupy the most disks ,root The directory is generally used by the system. It is better not to operate , Then switch to usr、var In both directories , Use du -h --max-depth=1 The command checks which directory occupies the most disk , Check it out in turn , Find the directory that uses the most disk , Then delete the unimportant files , For example, some log files , I this question , Finally, find nacos The log file of takes up more than 60 G Of disks , The final will be nacos Just delete these log files

Explain ,MySQL At startup, you will check the remaining disk space , If your disk is full , And stopped MySQL service , Then it can not be started at this time , After the disk needs to be cleaned , The remaining space is greater than 4G To start .

Generally speaking, servers cpu、 Memory 、 Warning values should be set for resources such as disks , When the usage reaches the warning value, you need to check the cause or increase the corresponding resources of the server ; For example, set the disk usage to 90% Give an early warning , When the alert is triggered, you need to find out what causes so many disks to be used , If some unimportant or useless files occupy a lot of disks , Then you can delete these files , If these files need to be retained, the files should be deleted after backup or the server disk space should be increased .