ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vyacheslav Koptilin (Jira)" <j...@apache.org>
Subject [jira] [Updated] (IGNITE-12152) Disk space not getting released after deleting rows from a table or after records expired with expiration policy
Date Tue, 10 Sep 2019 09:14:01 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-12152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Vyacheslav Koptilin updated IGNITE-12152:
-----------------------------------------
    Description: 
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.

 

 

  was:
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.

 

 


> 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.3.2#803003)

Mime
View raw message