[
https://issues.apache.org/jira/browse/RATIS-133?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16248273#comment-16248273
]
Mukul Kumar Singh commented on RATIS-133:
-----------------------------------------
Thanks for review [~jingzhao]. I did see the config to set the max message size
using "raft.grpc.server.message.size.max". However with Ozone when large
message size is set i.e 32MB/64MB. I was able to see the stack trace mentioned
on the bug. This bug adds a config so that we can check the message size on the
client (both RaftClient as well as AppendStreamer) to make sure that none of
the client is sending messages larger than the max size.
As noted in this jira, this will avoid the server side handling of the
StatusRunTimeException and the client will have to handle the message size.
> Raft gRPC client should check proto size before sending a message
> -----------------------------------------------------------------
>
> Key: RATIS-133
> URL: https://issues.apache.org/jira/browse/RATIS-133
> Project: Ratis
> Issue Type: Bug
> Reporter: Mukul Kumar Singh
> Assignee: Mukul Kumar Singh
> Priority: Critical
> Attachments: RATIS-133.001.patch
>
>
> Raft client should check the entry size before the command is send, This can
> otherwise lead to StatusRuntimeException. Checking the size on the client
> will help avoiding error handling on the RaftServer.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
