grpc: Increase message limits #470

Merged
fyrchik merged 1 commit from dstepanov-yadro/frostfs-node:fix/grpc_message_size into master 2023-06-30 13:52:05 +00:00

For send message limit set to 2GiB, but there are custom GET/GET RANGE limiters.
For receive message limit set to 256 MiB, but actual chunk size will be managed by client.

See #77

Signed-off-by: Dmitrii Stepanov d.stepanov@yadro.com

For send message limit set to 2GiB, but there are custom GET/GET RANGE limiters. For receive message limit set to 256 MiB, but actual chunk size will be managed by client. See https://git.frostfs.info/TrueCloudLab/frostfs-node/issues/77 Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
dstepanov-yadro requested review from storage-core-committers 2023-06-26 15:33:33 +00:00
dstepanov-yadro requested review from storage-core-developers 2023-06-26 15:33:33 +00:00
dstepanov-yadro force-pushed fix/grpc_message_size from aa80989b01 to c12dff7708 2023-06-26 15:34:18 +00:00 Compare
acid-ant reviewed 2023-06-26 18:36:21 +00:00
@ -22,3 +24,3 @@
grpcconfig.IterateEndpoints(c.appCfg, func(sc *grpcconfig.Config) {
serverOpts := []grpc.ServerOption{
grpc.MaxSendMsgSize(maxMsgSize),
grpc.MaxRecvMsgSize(maxRecvMsgSize),
Member

Why not to move it in config file?

Why not to move it in config file?
Author
Member

If we transfer this parameter to the configuration file, then we can get a situation where different nodes have different values set. This will lead to problems with requests.

If we transfer this parameter to the configuration file, then we can get a situation where different nodes have different values set. This will lead to problems with requests.
Member

We will face this error (if it will be) anyway because it is impossible to upgrade all nodes at once, rolling upgrade is a usual case for us.

We will face this error (if it will be) anyway because it is impossible to upgrade all nodes at once, rolling upgrade is a usual case for us.
Author
Member

Well, you are right.
We can prevent invalid configuration, but we can't prevent rolling upgrade.

Well, you are right. We can prevent invalid configuration, but we can't prevent rolling upgrade.
Owner

We have increased message size, so no problems should appear when talking old -> new node.
For new -> old we still use default chunkSize.

We have _increased_ message size, so no problems should appear when talking `old -> new` node. For `new -> old` we still use default `chunkSize`.
aarifullin approved these changes 2023-06-29 09:07:58 +00:00
dstepanov-yadro force-pushed fix/grpc_message_size from c12dff7708 to 53e54aa2c9 2023-06-30 08:38:07 +00:00 Compare
fyrchik approved these changes 2023-06-30 12:58:17 +00:00
dstepanov-yadro force-pushed fix/grpc_message_size from 53e54aa2c9 to 0c5b025788 2023-06-30 13:32:42 +00:00 Compare
fyrchik merged commit 0c5b025788 into master 2023-06-30 13:52:05 +00:00
fyrchik referenced this pull request from a commit 2023-06-30 13:52:06 +00:00
acid-ant approved these changes 2023-07-01 13:30:19 +00:00
Sign in to join this conversation.
No reviewers
No milestone
No project
No assignees
4 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/frostfs-node#470
No description provided.