[MAGNOLIA-5763] cachestream123456.tmp files are not removed from tmp directly Created: 05/May/14  Updated: 03/Jul/14  Resolved: 28/May/14

Status: Closed
Project: Magnolia
Component/s: cache
Affects Version/s: 4.5.8
Fix Version/s: 4.5.20

Type: Bug Priority: Major
Reporter: Tobias Mattsson Assignee: Milan Divilek
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Attachments: File Store.class    
Issue Links:
Cloners
clones MAGNOLIA-3681 Cache should remove streaming files w... Closed
is cloned by MGNLCACHE-58 CLONE - cachestream123456.tmp files a... Closed
relation
is related to MAGNOLIA-4568 Cache temp files are not cleared out ... Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Bug DoR:
[ ]* Steps to reproduce, expected, and actual results filled
[ ]* Affected version filled
Release notes required:
Yes
Date of First Response:

 Description   

The cache module leave behind files on tmp directory that it use for streaming large files. Reproducable on linux for big media files.

How to reproduce:
1) When the cache module tries cache big file (>512KB).
2) When the cache stream is interupted in cache big file process.

It was discussed This forum page



 Comments   
Comment by Jan Haderka [ 06/May/14 ]

hmm, it actually seems that at least some of those files have deleteOnExit set and are wiped out when you restart server, unless it is killed by admin.

Comment by Roman Kovařík [ 23/May/14 ]

Minor remarks:

  1. Please remove fix version 5.2.x and create ticket for cache module if necessary.
  2. Task name and description could be auto generated + description could point to the corresponding directory dynamically (Path.getTempDirectory()):
    public RemoveCacheTempFilesTask(String taskName, String taskDescription)
    
Comment by Jan Haderka [ 23/May/14 ]

@roman 5.2.x was meant for integration ... issue is same in 4.5.x and 5.2.x and 5.3 ... if we fix it, it needs to go upstream as well, but not necessarily in 5.2.5

Generated at Mon Feb 12 04:08:09 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.