Can someone please tell me exactly what happens when the DM OptimizeDB.js operation is run? We recently had a BU DMA’s disk get completely full when it should have had ~ 200G of free space. The database is large and on the BU DMA there is a table which is 136G in file size but only has the same number of records as the matching table on the PRI DMA which is only 37G in size. This indicates to me that this table on the BU DMA is not getting Optimized. I am wondering if during one of the Optimization operations on the BU DMA that the operation used up the remaining disk space on the server causing the process to fail and the problem with a full disk.
Thanks for any advice.
Hi Jeff,
OptimizeDB.js basically tells the SLDMS process to start optimizing the tables in MySQL. This is done by executing the OPTIMIZE TABLE queries on MySQL. The goal of this optimization is to reduce disk usage.
In the background MySQL will create a temporary file with the reorganized tables, which may use a lot of disk space if you have very large tables. So I think it’s indeed possible that you’re running out of disk because of this process.