Number of gRPC PUT operations is always twice the number of s3 requests #102
Labels
No labels
P0
P1
P2
P3
good first issue
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
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-s3-gw#102
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
With a load flow in 1 REP, the number of gRPC PUT operations is always twice the number of s3 requests.
For example:
CID:
The same issue is actual and for REP2. For example:
@a.bogatyrev can you provide exact metric names which are used in those graphs?
This happens when you upload object to the node out of placement. Then one S3 requests produced two gRPC requests: one from gateway to node and one redirection from node to another node by placement policy.
Also make sure to filter
api
labels infrostfs_s3_requests_total
, because it might include other operations besidesPutObject
./cc @a.bogatyrev