Raven888888 commented on issue #31564: URL: https://github.com/apache/doris/issues/31564#issuecomment-1973242222
@HHoflittlefish777 We managed to "fix" it by re-creating the table and copy the data over, then the data starts consuming in the routine load. But I would not call it a "fix". Not sure how/why the table got "corrupted". As I recall, these are what we did on the table before the incident happens: 1. Because the table gets too big, we `delete` some older data in the table. 2. After more than a day, the table size did not get smaller, storage is not released. We issued `ADMIN CLEAN TRASH;` 3. We also increased the partitions of the table from replication number = 1 to 3. 4. Then the incident happens. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@doris.apache.org For additional commands, e-mail: commits-h...@doris.apache.org
