[#479] Fix writecache fstree flush premature ctx cancel #518
No reviewers
TrueCloudLab/storage-core-developers
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 milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#518
Loading…
Reference in a new issue
No description provided.
Delete branch "ale64bit/frostfs-node:fix/479-wc-fstree-flush"
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?
The context is guaranteed to be canceled if
Close
is called, since the waitgroup is waited upon there.Signed-off-by: Alejandro Lopez a.lopez@yadro.com
Closes #479
writecache:
prefix to the commit message?3e5af91864
to11027945d8
done
<rant>
This practice seems rather futile. It's not enforced anyhow. It's not used in any kind of automation. There's not even an authoritative list of the valid component names or prefixes. What are we gaining with this?
</rant>
Uniform commit messages across the codebase.
It is useful for reading code and searching for commits.
We could change this, but anyway, please, let's discuss it first, so everyone is aware.