[HDDS-5393] Return latest version of key location for client on createKey/createFile

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Fix Version/s: 1.2.0
• Component/s: Ozone Client
• Labels: pull-request-available
• Assignee: Bharat Viswanadham
• Reporter: UENISHI Kota
• Created: 28/Jun/21 03:36
• Updated: 24/Aug/21 17:08
• Resolved: 24/Aug/21 17:08

Description

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.

Issue Links

• depends upon: HDDS-5243 Return latest version of key location for client
• is fixed by: HDDS-5461 Move old objects to delete table on overwrite
• links to: GitHub Pull Request #2432