[
https://issues.apache.org/jira/browse/HDDS-11774?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18038777#comment-18038777
]
Sumit Agrawal commented on HDDS-11774:
--------------------------------------
We need not fix this as,
# This is bug in server that list size is not guarded and causes OOM issue
# user expecting to be huge size need adjust its logic with batching
So having default max list size 1000 is reasonable for old client also.
Otherwise support old client to have all items can result in bug of OOM.
Further this is a year old and may not need support now also as most of them
got upgraded.
> Adding ozone.om.server.list.max.size breaks older version client compatibility
> ------------------------------------------------------------------------------
>
> Key: HDDS-11774
> URL: https://issues.apache.org/jira/browse/HDDS-11774
> Project: Apache Ozone
> Issue Type: Bug
> Reporter: Swaminathan Balachandran
> Assignee: Swaminathan Balachandran
> Priority: Major
> Labels: pull-request-available
>
> As part of a HDDS-11696 a config ozone.om.server.list.max.size which caps the
> maximum number of response objects. As part of this patch we changed the
> Ozone FS client's pagination logic as well to fire another request till the
> client receives a non empty reponse. This change on the server side is not
> compatible with older clients.
> Adding this info about client info to listing metadata can be added to fix
> the issue which would allow the server to understand if the client would be
> able to handle the server side.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
