neils-dev commented on code in PR #3297:
URL: https://github.com/apache/ozone/pull/3297#discussion_r854713179
##########
hadoop-hdds/common/src/main/resources/ozone-default.xml:
##########
@@ -3040,7 +3039,14 @@
OM/SCM/DN/S3GATEWAY Server connection timeout in milliseconds.
</description>
</property>
-
+ <property>
+ <name>ozone.om.grpc.maximum.response.length</name>
+ <value>134217728</value>
Review Comment:
This is enforced by the both the client and server as we define the limit,
max message size. In the case of listing, the server will feed the payload
within the` OMResponse` and the length of the message is enforced by the client
in this case. It raises a `RESOURCE_EXHAUSTED - message length exceed` io.grpc
exception. This occurs when the message passed from the server to the client
exceeds the incoming max message length.
Thanks @kerneltime, in looking into handling this exception I found that it
needs to be isolated by the failover proxy provider `retryPolicy` to _fail_
(not retry) on calling the `shouldFailover` method. The failover provider and
`retryPolicy shouldFailover` is currently refactored and will be included in
HDDS-6433 that will be commited to the Master after the feature branch merge.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
