After deleting an object, it is available #544
Labels
No Label
P0
P1
P2
P3
badger
frostfs-adm
frostfs-cli
frostfs-ir
frostfs-lens
frostfs-node
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No Milestone
No project
No Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#544
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may exist for a short time before cleaning up, in most cases it CANNOT be undone. Continue?
Expected Behavior
After we have created a container, loaded an object into it and deleted the object, we expect that we will not be able to get the object.
Current Behavior
With varying frequency, we can get the object after it has been deleted.
Steps to Reproduce (for bugs)
frostfs-cli --rpc-endpoint 127.0.10.1:8080 --wallet /path/to/wallet container create --policy 'REP 2 CBF 2 SELECT 2 FROM *'
OUT:
container ID: <CID>
frostfs-cli --rpc-endpoint 127.0.0.1:8080 --wallet /path/to/wallet object put --cid <CID> --file /path/to/file
OUT:
[/path/to/file] Object successfully stored OID: <OID> CID: <CID>
frostfs-cli --rpc-endpoint 127.0.0.1:8080 --wallet /path/to/wallet object delete --oid <OID> --cid <CID>
OUT:
Object removed successfully. ID: <OID> CID: <CID>
frostfs-cli --rpc-endpoint 127.0.0.1:8080 --wallet /path/to/wallet object get --oid <OID> --cid <CID> --file /tmp/file
OUT:
[/out/path/file] Object successfully saved ID: <OID> CID: <CID> Owner: <OwnerID> CreatedAt: 10 Size: 134217728 HomoHash: <empty> Checksum: <SUM> Type: REGULAR Attributes: FileName=NameFile Timestamp=<TIMESTAMP> ID signature: public key: <publicKey> signature: <SIGNATURE>
Your Environment
VM 8 nodes
Debian
Unable to reproduce in dev-env, @d.zayakin please provide storage logs once you face this issue again.
Have you tried both big and small objects?
Yes, I did with objects of both sizes
The same, tried to reproduce with complex object too.
Tried with three containers with following policies:
Randomly choose
cids
and following predefined payloads:No luck, unfortunately, still unable to reproduce in dev-env.
MaxObjectSize: 4096
@d.zayakin unable to reproduce it too, let's close.