Deleted container sporadically appears in the container list immediately after deletion #506
Labels
No labels
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 project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#506
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
When a container is deleted with "frostfs-cli container delete" and then "frostfs-cli container list" is invoked immediately after, the container is sometimes (with the probability of around 30%) present in the list. It goes away in several seconds, presumably after the morph.cache_ttl interval expires.
Expected Behavior
The deleted container is never present in the container list.
Current Behavior
The deleted container is sometimes (with the probability of around 30%) present in the list and goes away in several seconds, presumably after the morph.cache_ttl interval expires.
Possible Solution
No fix can be suggested by a QA engineer. Further solutions shall be up to developers.
Steps to Reproduce (for bugs)
Since the check uses frostfs-cli commands, performing the container create, delete and list commands manually should cause the problem to manifest too.
Context
This issue causes the tatlin-object-check command (used to check the cluster health) to fail sporadically.
Regression
No.
Your Environment
A SberCloud cluster, T.O 1.3.0-41.
I'm not able to repro this. I've tried in dev-env with different values of epoch duration and morph ttl cache.
Here's the script I'm using: