-
Type:
Bug
-
Status: Resolved
-
Priority:
Minor
-
Resolution: Fixed
-
Affects Version/s: 2023.0, 2021.38
-
Component/s: Bulk
-
Release Notes Summary:The deletedSize and totalSize of the bulk status result returned by Blob GC are now correct
-
Tags:
-
Team:PLATFORM
-
Sprint:nxplatform #99
-
Story Points:3
When auditing a Full Blob GC bulk status, we have :
{
"entity-type": "bulkStatus",
"commandId": "d09a542b-0fca-4419-9b4c-3da9ab9bd3c6",
"state": "COMPLETED",
"processed": 30713,
"skipCount": 25941,
"error": false,
"errorCount": 0,
"total": 30713,
"action": "garbageCollectOrphanBlobs",
"username": "system",
"submitted": "2023-10-13T15:16:04.086Z",
"scrollStart": "2023-10-13T15:16:04.184Z",
"scrollEnd": "2023-10-13T15:16:48.054Z",
"processingStart": "2023-10-13T15:16:48.081Z",
"processingEnd": "2023-10-13T15:17:18.727Z",
"completed": "2023-10-13T15:17:18.762Z",
"processingMillis": 59850,
"result": {
"dryRun": true,
"deletedSize": 1334005466,
"totalSize": 1838407952,
"merge": true
}
}
while in server.log we can see
Scrolled 30713 objects of total size 53 GB
which does not match
"totalSize": 1838407952,
This was observed on an s3 bucket of which the total size was 53GB
- is related to
-
NXP-28565 Make orphan binaries GC scalable
-
- Resolved
-
