You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by GitBox <gi...@apache.org> on 2020/06/12 14:11:43 UTC

[GitHub] [hadoop-ozone] bshashikant commented on pull request #1068: HDDS-3611. Ozone client should not consider closed container error as failure.

bshashikant commented on pull request #1068:
URL: https://github.com/apache/hadoop-ozone/pull/1068#issuecomment-643291103


   Thanks @lokeshj1703 for working on this. The change looks ok. 
   I think in this case, ozone client has already exhausted the max attempt count trying to write the data but eventually failed .
   
   How about this case, where the client attempts to write and in turn run into ContainerNot open exception? In such cases, ozone client may keep on retrying for considerable amount of time which i think we should not do.
   
   May be its ok to fail irrespective of exception after trying for maximum attempts.
   Also, the test failure seems to be related. Can u plz check as well?


----------------------------------------------------------------
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.

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



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