Error "could not put object to BLOB storage: context canceled" should not increase shard errors #596
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
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-node#596
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?
Expected Behavior
Error "could not put object to BLOB storage: context canceled" increases shard errors.
Current Behavior
Error "could not put object to BLOB storage: context canceled" should not increase shard errors, because potential network problems can lead to change mode of shard to
degraded
.Steps to Reproduce (for bugs)
1.Start k6 load to system
2.See errors in log that increases errors count on shards:
Version
Your Environment
HW
It seems impossible to cleanly convert them to logical errors everywhere, I think we can check it in the
engine.reportError
, right close to where we check the "logicality".fyrchik referenced this issue2023-08-16 08:16:27 +00:00