Metabase upgrade optimizations #1355
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1355
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:feat/mb_upgrade_optimizations"
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?
metabase upgrade
concurrently 1e0cce3aa94ba6a9981b
toae282aec0a
ae282aec0a
to6512f86375
6512f86375
todf20a973c8
df20a973c8
toced3a8461a
ced3a8461a
to49702daced
49702daced
tob685d5861e
Please take a look at
CI -> Tests and linters / Lint
.b685d5861e
to4668efc0bf
@ -86,6 +90,7 @@ func compactDB(db *bbolt.DB) error {
}
dst, err := bbolt.Open(tmpFileName, f.Mode(), &bbolt.Options{
Timeout: 100 * time.Millisecond,
NoSync: true,
We can leave garbage in case of premature exit, do we handle this somehow?
It is a problem, because we can have no space and need to describe what to do.
No.
I dont want to do some delete by pattern to not to delete some manual created files.