frostfs-node refactorings #168
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
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#168
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-node:refactoring/OBJECT-3610_node"
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?
4254f4efca
toe50d119107
1da212f3e9
to4f619c99a5
WIP: frostfs-node refactoringsto frostfs-node refactorings@ -93,1 +117,4 @@
)
}
func addEpochHandler(c *cfg, eigenTrustController *eigentrustctrl.Controller) {
The name seems to generic, given the function signature.
fixed
@ -265,3 +266,3 @@
// Reload reloads StorageEngine's configuration in runtime.
func (e *StorageEngine) Reload(rcfg ReConfiguration) error {
func (e *StorageEngine) Reload(ctx context.Context, rcfg ReConfiguration) error {
It is tricky from the code POV: nothing prevents us from passing different contexts on
Init
andReload
-- this will lead to different shards living in different worlds (possibly, some of the shards exiting early).To me it looks, like storing the context somewhere in the
engine
is not so bad. cc @carpawell @ale64bitIMHO, neither the context should be stored in a struct (context docs discourage this explicitly) nor the state/functioning of the engine instance should depend on something stored in the context in the first place.
Dunno, it bugs be that this
ctx
is not a context for theReload
, but actually a context for the created shard.I would at least rename the variable or mention this in doc. But ok, if it seems good to you.
4f619c99a5
to018dd74f69
018dd74f69
to1c3a1cd39a
@ -1034,3 +1096,3 @@
c.setHealthStatus(control.HealthStatus_SHUTTING_DOWN)
c.ctxCancel()
c.done <- struct{}{}
may a closing be a more common way? it is more a question than a suggestion
1c3a1cd39a
toed28ce24cd