[
https://issues.apache.org/jira/browse/ASTERIXDB-564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14944463#comment-14944463
]
Murtadha Hubail commented on ASTERIXDB-564:
-------------------------------------------
This was fixed in commit ce70c7bb5cc9982a044fa9b2364da751442683ae.
It was tested manually and during normal operation (during high ingestion
workloads, you can see old log files being deleted). However, we don't have
actual test case for it. It is not a trivial thing to test with the existing
test framework since you would need to generate enough logs until a new log
partition is created, then wait for the non-sharp checkpoint to work and verify
that the old log partition was deleted.
> Log file Space reclamation during non-sharpcheckpoint and checkpoint thread
> implementation
> ------------------------------------------------------------------------------------------
>
> Key: ASTERIXDB-564
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-564
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: AsterixDB, Transactions
> Reporter: Young-Seok Kim
> Assignee: Murtadha Hubail
>
> Log file Space reclamation during non-sharpcheckpoint and checkpoint thread
> implementation
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
