-
Question descriptionQuestion 1When the object expires, mc stat can't get the object, but the minio drive corresponding disk directory of the object and xl.meta still exist. [root@minio-1 dx]# ls -l /export5/collect-ngaf-file-bucket0/20240508_NGAF_SECEVENT_blob_s_DB3EF0D2_data_MTA1NQ==_1715158837/
total 4
-rw-r--r-- 1 root root 443 May 8 17:04 xl.meta
[root@minio-1 dx]# mc stat myminio/collect-ngaf-file-bucket0/20240508_NGAF_SECEVENT_blob_s_DB3EF0D2_data_MTA1NQ==_1715158837
mc: <ERROR> Unable to stat `myminio/collect-ngaf-file-bucket0/20240508_NGAF_SECEVENT_blob_s_DB3EF0D2_data_MTA1NQ==_1715158837`. Object does not exist. At https://min.io/docs/minio/kubernetes/upstream/operations/concepts/scanner.html, ilm of expiration is not immediate. And my question is, when the expiration time is up, the expired object file is still on the instant disk, but when the get or stat request is executed, minio will tell the object does not exist. Is it normal? Question 2The bucket expiration time is set to one day, and the lifecycle rules are as follows: {
"status": "success",
"target": "myminio/collect-ngaf-file-bucket0",
"config": {
"Rules": [
{
"Expiration": {
"Days": 1
},
"ID": "cot1mnbte3cv7kish05g",
"Status": "Enabled"
},
{
"Expiration": {
"Days": 1
},
"ID": "cot1obbte3cn7cmrpseg",
"Status": "Enabled"
}
]
},
"updatedAt": "0001-01-01T00:00:00Z"
} The distribution of the data inside the bucket is as follows: [root@minio-1 dx]# mc stat myminio/collect-ngaf-file-bucket0
Name : collect-ngaf-file-bucket0
Date : 2024-05-09 20:36:43 CST
Size : N/A
Type : folder
Properties:
Versioning: Un-versioned
Location: us-east-1
Anonymous: Disabled
ILM: Enabled
Usage:
Total size: 9.9 GiB
Objects count: 583,855
Versions count: 0
Object sizes histogram:
486964 object(s) less than 1024 bytes
96891 object(s) between 1024 bytes and 1 MB
0 object(s) between 1 MB and 10 MB
0 object(s) between 10 MB and 64 MB
0 object(s) between 64 MB and 128 MB
0 object(s) between 128 MB and 512 MB
0 object(s) greater than 512 MB When the expiration time has passed 10 hours, there are 400,000+ small objects left, which is too many objects to use ls. The slow removal of stale objects may have something to do with the speed of the scanner. I change scanner speed=fast to see that the slope of the monitored freeinodes does not change. |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
Q1. Yes this is normal. Q2: Not correct. You can observe scanner speed with |
Beta Was this translation helpful? Give feedback.
-
And, why does |
Beta Was this translation helpful? Give feedback.
-
yep. I mean the expiration time is 5/10/2014 00:00 UTC(5/10/2014 10:00 CST). |
Beta Was this translation helpful? Give feedback.
Q1. Yes this is normal.
Q2: Not correct. You can observe scanner speed with
mc admin scanner info ALIAS
.