[
https://issues.apache.org/jira/browse/HDDS-5393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17370541#comment-17370541
]
UENISHI Kota commented on HDDS-5393:
------------------------------------
On overwriting, old blocks that belong to the former versions of the key must
be sent out to deleteKeyTable as they are eligible to be deleted unless the
bucket has turned object versioning on. It is not clear how to send them
atomically, without being committed, though.
Another option, send them back to openKeyTable, needs HDDS-4123 which is not
yet completed. HDDS-4123 seem to be in lower priority, as blocks that belong to
be stale is expected to be committed and eventually deleted, maybe in a far
future.
> Return latest version of key location for client on createKey
> -------------------------------------------------------------
>
> Key: HDDS-5393
> URL: https://issues.apache.org/jira/browse/HDDS-5393
> Project: Apache Ozone
> Issue Type: Improvement
> Components: Ozone Client
> Reporter: UENISHI Kota
> Priority: Major
> 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]
