Possible problems with XHeader processing #465
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
1 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#465
Loading…
Reference in New Issue
There is no content yet.
Delete Branch "%!s(<nil>)"
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?
We don't set netmap epoch XHeader for auxiliary queries in the object service
71a63b8e9c/pkg/services/object/internal/client/client.go (L84)
However, it seems we set it impliticly via the x-headers. It is a problem:
netmap_depth ^ TTL
(first node searches at epochs N..N-D+1, another nodes searches N..N-D+1, N-1..N-D etc.), because XHeaders are being sent unchanged.API description is vague
dbfa9c944b/session/types.proto (L145)
Let's discuss and fix the behaviour.
cc @alexvanin @realloc