You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@asterixdb.apache.org by "Chen Luo (JIRA)" <ji...@apache.org> on 2018/03/11 18:36:00 UTC

[jira] [Updated] (ASTERIXDB-2324) File Pages still exist after Deleting a File From BufferCache

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

Chen Luo updated ASTERIXDB-2324:
--------------------------------
    Description: The typical workflow for deleting an LSM index is to deactive, purge, and destroy. During deactive, we close the file. Then during purge, we should remove the file mapping and all file pages. Finally, during destroy, the file is physically deleted. However, BufferCache.purge didn't clear cached pages as specified. Even though delete file internally calls clear pages, which is never executed since the file mapping has already been removed. As a result, files pages are not removed even though the file is deleted.  (was: The typical workflow for deleting an index is to first deactive and then destroy. During deactive, we close the index file from the buffer cache, which internally removes the file info (however, the pages are still in the buffer cache). We then call destroy to delete that file. However, most callers use the file reference as the parameter, which causes file pages are not cleaned because the file info does not exist any more.)

> File Pages still exist after Deleting a File From BufferCache
> -------------------------------------------------------------
>
>                 Key: ASTERIXDB-2324
>                 URL: https://issues.apache.org/jira/browse/ASTERIXDB-2324
>             Project: Apache AsterixDB
>          Issue Type: Bug
>          Components: STO - Storage
>            Reporter: Chen Luo
>            Priority: Major
>
> The typical workflow for deleting an LSM index is to deactive, purge, and destroy. During deactive, we close the file. Then during purge, we should remove the file mapping and all file pages. Finally, during destroy, the file is physically deleted. However, BufferCache.purge didn't clear cached pages as specified. Even though delete file internally calls clear pages, which is never executed since the file mapping has already been removed. As a result, files pages are not removed even though the file is deleted.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)