Investigate and describe behaviour for invalid well-known attributes #1109

New issue

Closed

opened 2024-04-27 10:05:09 +00:00 by fyrchik · 2 comments

fyrchik commented

2024-04-27 10:05:09 +00:00

Owner

What if EXPIRATION_EPOCH is not a number, can we remove an object?
What if NNS_* or some other container attribute is bad?

All well-known attributes can be found in https://git.frostfs.info/TrueCloudLab/frostfs-api

What if EXPIRATION_EPOCH is not a number, can we remove an object? What if NNS_* or some other container attribute is bad? All well-known attributes can be found in https://git.frostfs.info/TrueCloudLab/frostfs-api

fyrchik added the

triage

label 2024-04-27 10:05:09 +00:00

fyrchik added this to the vNext milestone 2024-04-27 10:05:49 +00:00

fyrchik added

documentation

and removed

triage

labels 2024-04-27 10:05:57 +00:00

fyrchik modified the milestone from vNext to v0.39.0

2024-05-02 07:49:05 +00:00

acid-ant was assigned by fyrchik

2024-05-02 07:49:22 +00:00

fyrchik modified the milestone from v0.39.0 to vNext

2024-05-14 14:03:30 +00:00

acid-ant commented

2024-06-06 13:31:38 +00:00

Member

What if EXPIRATION_EPOCH is not a number, can we remove an object?

Iteration over expiration bucket in metabase will fail with error:

2024-06-06T13:16:50.759Z        warn    shard/gc.go:399 iterator over expired objects failed    {"shard_id": "KzhZZxxSiRAvBbastnXLEr", "error": "could not parse expiration epoch: strconv.ParseUint: parsing \"qeqeqeqqweqe\": invalid syntax"}

Object will never be removed by gc, also this stops processing of the other keys in a bucket.

> What if EXPIRATION_EPOCH is not a number, can we remove an object? Iteration over `expiration` bucket in metabase will fail with error: ``` 2024-06-06T13:16:50.759Z warn shard/gc.go:399 iterator over expired objects failed {"shard_id": "KzhZZxxSiRAvBbastnXLEr", "error": "could not parse expiration epoch: strconv.ParseUint: parsing \"qeqeqeqqweqe\": invalid syntax"} ``` Object will never be removed by `gc`, also this stops processing of the other keys in a bucket.

acid-ant commented

2024-06-07 07:46:53 +00:00

Member

NAME and ZONE attributes unable to affect somehow workflow because they are string.
There are no any other SYSTEM attributes

`NAME` and `ZONE` attributes unable to affect somehow workflow because they are string. There are no any other `SYSTEM` attributes

acid-ant referenced this issue from a pull request that will close it,

2024-06-18 12:11:49 +00:00

object: Validate attribute EXPIRATION_EPOCH on put #1188

fyrchik referenced this issue from a commit

2024-06-19 17:19:33 +00:00

[#1109] object: Validate attribute `EXPIRATION_EPOCH` on `put`

fyrchik closed this issue