Allow to specify max_obj_size #145
No reviewers
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
5 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#145
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/xk6-frostfs:feat/max_obj_size"
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?
Allow to override MAX_OBJECT_SIZE value for native protocol for locally prepared objects.
Tested on local setup.
534ad7ff9b
to6d1e7eb49e
@ -117,0 +123,4 @@
if err != nil {
return nil, err
}
if uint64(maxObjSize) > res.Info().MaxObjectSize() {
We fetch network info in
put()
, why not validate there?We can use the same client and multiple sizes in the same scenario, so
maxObjSize
is unrelated toConnect