[
https://issues.apache.org/jira/browse/HDDS-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17383304#comment-17383304
]
UENISHI Kota commented on HDDS-5393:
------------------------------------
Yes, my intention was to slim down data size both in the RockDB and in RPC. I
should have assigned myself before starting my work, but sorry, I wasn't sure I
could take my effort on this issue regarding my main work. But I'm not familiar
with new FSO and new protobuf, so I would happily discuss how do we merge and
improve our work.
> Return latest version of key location for client on createKey/createFile
> ------------------------------------------------------------------------
>
> Key: HDDS-5393
> URL: https://issues.apache.org/jira/browse/HDDS-5393
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Client
> Reporter: UENISHI Kota
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Fix For: 1.2.0
>
>
> HDDS-5243 was a patch for omitting unnecessary key locations for clients on
> reading. But the same warning of large response size observed in our cluster
> for putting data. The patch can also be ported for putting data, as long as
> until object versioning is supported.
> My hypothesis is: The large message was originally, and possibly maybe due to
> this warning and sudden connection close from client side on reading large
> message in Hadoop IPC layer, from Ozone Manager - which causes hopeless 15
> retries from RetryInvocationHandler. The retries create another entry in
> OpenKeyTable but they never moved to KeyTable because the key never gets
> commited.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
