Open yasiryagi opened 6 months ago
I am not fully convinced that these error refers to the above objectId:
Currently on uploads we rely on the following middlewares chain:
verifyUploadFileParams
middlewareOpenApiValidator.middleware
with multer
for uploads, into tempDirectory
If 1 throws then 2 is not called.
Once file upload has succesfully executed, the route handleruploadFile
is caled and basically moves the file to the pendingDirectory
after verifying the hash file
Once every 6s (i.e. every target block production rate) the AcceptPendingObject
service is called which processes objects in the pendingDirectory
and then issues the accepting transaction for each of these. Only after the tx is successfully issued the objects are either moved into the uploadDir
(from where they are actually served).
The errors describes appears to be Middleware errors (except for object 1713397
) for which Express returns an error and the following steps 2️⃣ and 3️⃣ are not pursued.
Objects 1713397
encounters a timeout error in the acceptPendingDataObjects
transaction.
I am investigating on the first object and:
{
"data": {
"storageDataObjectById": {
"isAccepted": true,
"storageBag": {
"id": "dynamic:channel:42488",
"storageBuckets": [
{
"id": "10-dynamic:channel:42488",
"storageBucket": {
"operatorMetadata": {
"nodeEndpoint": "https://storage2.sieemmastorage.com/storage/"
},
"id": "10"
}
},
{
"id": "1-dynamic:channel:42488",
"storageBucket": {
"operatorMetadata": {
"nodeEndpoint": "https://storage.mrbovo.xyz/storage/"
},
"id": "1"
}
},
{
"id": "2-dynamic:channel:42488",
"storageBucket": {
"operatorMetadata": {
"nodeEndpoint": "https://storage.joystream.8k.pm/storage/"
},
"id": "2"
}
},
{
"id": "3-dynamic:channel:42488",
"storageBucket": {
"operatorMetadata": {
"nodeEndpoint": "https://joystream.name/storage/"
},
"id": "3"
}
}
]
},
"acceptingBucketId": "12"
}
}
}
I think this is worth a task on his own and not be included in the s3 epic as it might be require more time and investigation than needed
Issue:
Uploads that has failed , but still marked as accepted on chain
Evidence:
dataObjectId: 2100687
dataObjectId: 2112736
dataObjectId: 1713397
dataObjectId: 2112361