objectwriter: Allow customize maxChunkLen #96
Labels
No labels
P0
P1
P2
P3
good first issue
pool
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/frostfs-sdk-go#96
Loading…
Reference in a new issue
No description provided.
Delete branch "dstepanov-yadro/frostfs-sdk-go:feat/customize_max_chunk_len"
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?
Closes #80
We can create some handler on frostfs-node to get server parameters. But actually we shoul ask every node from netmap about max send/receive size.
Now there is no option to change message size on node, so looks like this is not required now.
objectwriter: Allow custimize maxChunkLento objectwriter: Allow customize maxChunkLen4949931c82
tofed623ed91
@ -42,0 +44,4 @@
// Maximum chunk length restricts maximum byte length of the chunk
// transmitted in a single stream message. It depends on
// server settings and other message fields.
// If not specified or negative value set, default value of 3MB will be used.
s/MB/MiB/ ?
fixed
@ -42,0 +45,4 @@
// transmitted in a single stream message. It depends on
// server settings and other message fields.
// If not specified or negative value set, default value of 3MB will be used.
func (x *PrmObjectPutInit) SetMaxChunkLen(v int) {
I am now thinking: this setting is somewhat low-level and relates only to the gRPC. It is also confusing because we have
MaxObjectSize
in #94/ , which is alsoMaxChunkLen
in some sense.May we somehow reflect this in naming? cc @acid-ant
My suggestion would be:
SetgRPCPayloadChunkLen
(longer name communicates the complexity and creates cognitive load)SetObjectPartSize
for #94We surely can come up with something better. @TrueCloudLab/storage-core-committers @TrueCloudLab/storage-core-developers
fixed
I agree, that it is better to reflect in naming that this parameter relies on gRPC.
fed623ed91
toc243b443bc