Allow to split objects on client #75
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
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/xk6-frostfs#75
Loading…
Reference in a new issue
No description provided.
Delete branch "acid-ant/xk6-frostfs:feature/72-cut-obj-in-client"
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?
Close #72
Signed-off-by: Anton Nikiforov an.nikiforov@yadro.com
Usage examples:
72da79ffc2
to4726f23dfa
4726f23dfa
toa2d9e1ce55
a2d9e1ce55
toee0f8eeb12
ee0f8eeb12
to0bfbbe5d7e
WIP: Allow to split objects on clientto Allow to split objects on client0bfbbe5d7e
to2f9b35a146
@ -36,6 +36,8 @@ parser.add_argument('--ignore-errors', help='Ignore preset errors')
parser.add_argument('--workers', help='Count of workers in preset. Max = 50, Default = 50', default=50)
parser.add_argument('--sleep', help='Time to sleep between container creation and object PUT (in seconds), '
'Default = 8', default=8)
parser.add_argument('--prepare-locally', help='Generate object header on the client side (for big object - '
I don't think it is required for preset.
As discussed option was removed, but I prefer to keep ability to use this option in future(currently flag set to
False
).If we have no option, what is the motivation for having the code?
It wouldn't be hard to add it in future, but now we need to support it.
The idea is to test it, and, if we will find it useful, enable by default.
Removed from
preset
.2f9b35a146
to74fa95e665
74fa95e665
to4cbd7c9c70
4cbd7c9c70
toff6814e15d