metabase: optimize Inhume
operation #1385
No reviewers
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#1385
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:fix/metabase_inhume_hangs"
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?
During load testing, a high latency (> 5s) was detected when performing an
Inhume
operation.Fixed:
Update
replaced withBatch
in metabase: based on the analysis of pprof data, it can be seen that singleUpdate
operations in the metabase take a long timeisTomb
check that checks that inhumed object is not tombstone: now it checks only objects from the same containerTOMBSTONE
stores objectIDs as members, also seeInhume
call fromDelete
RPC:addrs[i].SetContainer(tombstone.Container())
Inhume latency before:
Inhume latency after:
Batch
for delete-related operationsc1b4c5c0a0
toa193465421
metabase: Useto WIP: metabase: UseBatch
for all concurrent operationsBatch
for all concurrent operationsisTomb
check2e35eff8cb
tob15437c947
WIP: metabase: Useto metabase: optimizeBatch
for all concurrent operationsInhume
operationb15437c947
to3b5a9d466f
Please rebase on master.
3b5a9d466f
tofd18aa363b