You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "mingchao zhao (Jira)" <ji...@apache.org> on 2022/01/13 13:50:00 UTC

[jira] [Resolved] (HDDS-5946) The 'Cannot allocate Memory 'problem occurs in client while test write

     [ https://issues.apache.org/jira/browse/HDDS-5946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

mingchao zhao resolved HDDS-5946.
---------------------------------
    Resolution: Workaround

The HDDS-6138 will fix this

> The 'Cannot allocate Memory 'problem occurs in client  while test write
> -----------------------------------------------------------------------
>
>                 Key: HDDS-5946
>                 URL: https://issues.apache.org/jira/browse/HDDS-5946
>             Project: Apache Ozone
>          Issue Type: Sub-task
>            Reporter: mingchao zhao
>            Assignee: mingchao zhao
>            Priority: Major
>              Labels: pull-request-available
>         Attachments: BlockingQueue.patch, screenshot-2.png, screenshot-3.png
>
>
> When I tested write performance with the new client, I got the following exception 
>  !screenshot-2.png! 
> I found the problem started after we implemented retry in HDDS-5674.  In the test, I used a single client to write 400 files concurrently. and each file 128MB. The client's memory will become much larger than before.
>  !screenshot-3.png! 
> The reason for this is that bufferList is used in Retry to maintain references to all byteBuffers currently being written. The client will hold those references to byteBuffer until commit the block.  In the past, all Bytebuffers were released after they were sent, but now we need to wait for write successful before releasing. So now the client will accumulate more Bytebuffers and need more memory.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org