[GitHub] [ozone] bshashikant commented on pull request #2835: HDDS-5946. [Ozone-Streaming] The 'Cannot allocate Memory 'problem occurs in client while test write

[GitBox <gi...@apache.org>]

bshashikant commented on pull request #2835:
URL: https://github.com/apache/ozone/pull/2835#issuecomment-981285909


   > Hi @szetszwo @bshashikant @sadanand48 I just updated the PR with the idea of [HDDS-5852](https://issues.apache.org/jira/browse/HDDS-5852). At present, the PR can support: 1、Ensure that putBlock is executed when an exception occurs, but we need allow to execute putBlocks to closed containers. 2. After chunk is successfully written, it will be cleared immediately. I'm not using the previous window approach because testing found that it would degrade performance. If there are other suggestions, we can continue the discussion here.
   
   Why it needs to allow putBlock on closed containers?? this will break the open-close container semantics. In my opinion, it doesn't need do. We need to handle closed container exception on the client and retry from last committed and ack'd data length for a block to a new block altogether.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



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