Replies: 3 comments 3 replies
-
|
My main question -> why lifecycle job does not start each day? |
Beta Was this translation helpful? Give feedback.
-
|
From https://docs.aws.amazon.com/AmazonS3/latest/userguide/intro-lifecycle-rules.html
Sounds like you are just seeing expected behaviour. |
Beta Was this translation helpful? Give feedback.
-
|
Hello again, everyone. I waited a while as the s3 documentation suggested and... nothing was cleaned up. My bucket currently has 19 terabytes of space, with 2 terabytes left before maxing out. Here's the output of ilm ls (please ignore the name of the rule, I used to set it to 10 days, but on 08/22/2025 I changed the rule to 14 days.) -> Here's the output of scanner settings (I suppose this data is worth sharing as well) -> Here's the same cleanup schedule screendshot, only after another day.. -> MiniO simply didn't run the cleanup task >48 hours, although it's critical for me. It all looks sad.. |
Beta Was this translation helpful? Give feedback.
-
|
Seems you have a whole lot of delete markers. See the section on If this is critical get a subscription. |
Beta Was this translation helpful? Give feedback.
-
|
@harshavardhana Hello! Sorry for tagging you in this way, could you please look into my question and help me solve it? |
Beta Was this translation helpful? Give feedback.
-
|
@bobdan122 We do not provide personal community support, so don't tag random people. If you would like personal SLA-driven support reach out on |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
NOTE
If this case is urgent, please subscribe to Subnet so that our 24/7 support team may help you faster.
I have a Minio cluster consisting of 4 nodes. Each node has 1 disk, the size of which is 7 TB. Minio is running in EC:1 mode with a storage utility of 21 TB.
The problem is in data cleanup ->
Expected Behavior
-> With the Lifecycle settings I'll provide below in JSON format:
{
"Rules": [
{
"ID": "DeleteEverythingAfter10Days",
"Status": "Enabled",
"Filter": {},
"Expiration": {
"Days": 14
},
"NoncurrentVersionExpiration": {
"NoncurrentDays": 1
},
"AbortIncompleteMultipartUpload": {
"DaysAfterInitiation": 1
}
}
]
}
I expect that once an object's upload date to the store is older than the 14-day period, the object will be deleted. This is critical because 1.5 TB of data is added to the store every day.
I also configured Prometneus to collect metrics and output this data to Grafana. From the graph of the metric "minio_node_ilm_action_count_delete_action" I see that many objects were deleted.
You can see the graph of object deletions.
Current Behavior
At the moment, the difference between the end time of the last iteration of cleaning is more than a day.
Possible Solution
Steps to Reproduce (for bugs)
Context
described in general summary
Regression
Your Environment
minio --version):My minio version is:
minio version RELEASE.2025-06-13T11-33-47Z
Runtime: go1.24.4 linux/amd64
License: GNU AGPLv3 - https://www.gnu.org/licenses/agpl-3.0.html
Copyright: 2015-2025 MinIO, Inc.
node01-03 -> 8cpu/16ram/ each node have 1disk with 7tb capacity
node04 -> on this node scanner running, that is why 16cpu/24ram/7tb
uname -a): Linux minio01(02,03,04) 5.15.0-143-generic Check for the installed golang version #153-Ubuntu SMP Fri Jun 13 19:10:45 UTC 2025 x86_64 x86_64 x86_64 GNU/LinuxBeta Was this translation helpful? Give feedback.
All reactions