[
https://issues.apache.org/jira/browse/IGNITE-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17544304#comment-17544304
]
Sergey Chugunov commented on IGNITE-12152:
------------------------------------------
[~shm] , this is expected behavior for 2.7 version, Storage Engine
implementation of Apache Ignite cannot free up disk space on the fly due to how
storage is designed on the most fundamental level.
Yet it is possible to reclaim disk space back in a newer versions starting from
2.10 using mechanism of defragmentation and Maintenance Mode. I added a link to
the ticket where CLI API was implemented for defragmentation.
If you don't mind I'll close the ticket with "Won't Fix" resolution.
> Disk space not getting released after deleting rows from a table or after
> records expired with expiration policy
> ----------------------------------------------------------------------------------------------------------------
>
> Key: IGNITE-12152
> URL: https://issues.apache.org/jira/browse/IGNITE-12152
> Project: Ignite
> Issue Type: Bug
> Components: documentation, persistence, sql
> Affects Versions: 2.7
> Reporter: shivakumar
> Priority: Critical
>
> To reproduce,
> create a cache group and create a sql table using that cache group, then
> insert considerable rows of records to the table, monitor the disk space
> usage, now stop inserting records and delete records from the table using
> *DELETE FROM table; (not a drop table operation)*
> once this is done the *select count(\*) from table;* shows the count 0 but
> after this when disk space is monitored it will be in the same usage level as
> it is in the level before rows deletion.
> When I start inserting records again, the new records re-used the space
> occupied by the deleted records but still, it is not a good idea to
> unnecessarily hold disk resource.
> The same can be reproduced by configuring cache expiry policy
> (CreatedExpiryPolicy) where after records expires it will not be visible in
> sql query (select * from table) but still it will hold disk resource.
>
>
--
This message was sent by Atlassian Jira
(v8.20.7#820007)
