engine: Drop shards weights #1005
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 Assignees
3 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#1005
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "dstepanov-yadro/frostfs-node:feat/drop_shard_weight"
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?
Now
Shard.FreeSpace
is always 0, so weights are unusedShard.FreeSpace
is not the best weight metricUsing weights requires redundant memory allocations
9e1edd70b7
tob250b9e8de
Can we make an additional test here? (expect it to pass).
SortHasherSliceByValue
If it is not, we can slowdown on update.
@ -26,4 +26,2 @@
WriteCacheInfo writecache.Info
// Weight parameters of the shard.
WeightValues WeightValues
Could affect frostfs-testcases, do we output this in frostfs-cli?
There is no weights in shard info.
b250b9e8de
to2ad433dbcb
Done