You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
In settings.pyt i have set the orphan cleanup time to ORPHAN_PROTECTION_TIME=1440. However i recently noticed that orphans aren't cleaned up.
A call on the cmd-line pulp orphan cleanup --protection-time 2880 which is twice the timer in the settings should provide 0 orphans to cleanup, if there is a periodic task running to clean up.
It seems the orphan task is running based on this output, but it is restricted to uploads and temporary files ?
I just re-read the config and maybe i am expecting something which is just not there by design. Given the below docs it implies that it is not when there is a task running to clean up orphans, but what the criteria are to clean up orphans after X time. If so, is it still a possibility to schedule an orphan clean up task, or would that be a feature request ?
The time specified in minutes for how long Pulp will hold orphan Content and Artifacts before they become candidates for deletion by an orphan cleanup task. This should ideally be longer than your longest running task otherwise any content created during that task could be cleaned up before the task finishes. Default is 1440 minutes (24 hours).
UPLOAD_PROTECTION_TIME, TMPFILE_PROTECTION_TIME and TASK_PROTECTION_TIME¶
Pulp uses tasks, uploads and pulp temporary files to pass data from the api to worker tasks. These options allow to specify a timeinterval in minutes used for cleaning up stale entries. If set to 0, automatic cleanup is disabled, which is the default.
You are reading correctly. The ORPHAN_PROTECTION_TIME behaves different from the others. It is that way, because we weren't confident enough yet to change existing behaviour with respect to orphan cleanup.
So yes, this sounds pretty much like a feature request.
Version
"versions": {
"deb": "3.3.1",
"gem": "0.6.1",
"rpm": "3.27.1",
"core": "3.62.0",
"file": "3.62.0",
"maven": "0.8.1",
"ostree": "2.4.3",
"python": "3.12.3",
"ansible": "0.22.1",
"certguard": "3.62.0",
"container": "2.21.0"
},
Describe the bug
In settings.pyt i have set the orphan cleanup time to
ORPHAN_PROTECTION_TIME=1440
. However i recently noticed that orphans aren't cleaned up.relevant settings
A call on the cmd-line
pulp orphan cleanup --protection-time 2880
which is twice the timer in the settings should provide 0 orphans to cleanup, if there is a periodic task running to clean up.It seems the orphan task is running based on this output, but it is restricted to uploads and temporary files ?
if i limit it to orphan_cleanup i only see tasks that are manually triggerd
To Reproduce
no idea
Expected behavior
orphan cleanup should run periodically, with regards to the setting ORPHAN_PROTECTION_TIME
Additional context
none
The text was updated successfully, but these errors were encountered: