Project

General

Profile

Actions

Bug #70928

closed

Garbage collection of entries without tags fail

Added by Gernot Leitgab over 8 years ago. Updated about 7 years ago.

Status:
Closed
Priority:
Must have
Assignee:
-
Category:
Caching
Target version:
-
Start date:
2015-10-21
Due date:
% Done:

0%

Estimated time:
TYPO3 Version:
6.2
PHP Version:
Tags:
Complexity:
Is Regression:
No
Sprint Focus:

Description

Due to the join statement entries without tags are never deleted from the database backend by the garbage collector.


Related issues 1 (0 open1 closed)

Follows TYPO3 Core - Bug #61814: Caching framework garbage collection scheduler task taking ages with database backend and large websitesClosed2014-09-23

Actions
Actions #1

Updated by Stephan Großberndt about 8 years ago

  • Status changed from New to Needs Feedback

I guess you are referring to this change: http://review.typo3.org/33254

The JOIN statement is only used if flushing by tags - then you explicitly want to remove only those with the tag. If all caches are cleared flush() is used instead of flushByTag() where the table is truncted and no JOIN is used.

Please explain in more detail what is wrong in your opinion if this is not the problem you want to report.

Actions #2

Updated by Gernot Leitgab almost 8 years ago

The problem is, that entries without tags are removed after clearance of all caches only, but the garbage collector will never remove them, so a manual admin interation is required. Especially on large installations this is a problem, because the database will grow very fast. I did a quick fix (actually working on MySQL only I think) for now, during the next few days I'll have a closer look on that problem and provide a fix for it.

Actions #3

Updated by Stefan Froemken over 7 years ago

I have just looked into the current master. There you have a query to remove all old cache entries incl. their tags AND, that is new, remove all tags which does not have a relation to an cache entry anymore.
I don't know why this was not backported, but with an own extension you can implement that feature update save to TYPO3 6.2 via: $GLOBALS['TYPO3_CONF_VARS']['SYS']['Objects'][$className]

Actions #5

Updated by Christian Kuhn about 7 years ago

I think this was fixed in master, 7.6 and 6.2 see https://review.typo3.org/#/c/49907/

Actions #6

Updated by Christian Kuhn about 7 years ago

  • Status changed from Needs Feedback to Closed
Actions

Also available in: Atom PDF