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/03/14 04:11:19 UTC

[GitHub] [hadoop-ozone] lokeshj1703 edited a comment on issue #673: HDDS-3064. Get Key is hung when READ delay is injected in chunk file path.

lokeshj1703 edited a comment on issue #673: HDDS-3064. Get Key is hung when READ delay is injected in chunk file path.
URL: https://github.com/apache/hadoop-ozone/pull/673#issuecomment-599001121
 
 
   @adoroszlai @bshashikant I am not saying we wait for the entire block to be read. The client will be reused for all the chunk reads. Lets take a scenario.
   Chunk1 fails on dn1. Succeded on dn2.
   Chunk2 -> we should try reading from either dn2 or dn3. We will need to mark dn1 timed out in the code. Currently we can still retry dn1.
   Chunk3 -> dn2, dn3 fail. We should retry dn1 before failing the read.
   For retrying dn1 we will need to reestablish the connection. I think we are handling this.
   
   Regarding the deadline, if we set a deadline at t=0, the stub will fail at t=30 even if the client is able to read chunks from the stub. Please verify if this is how the deadline works. I think we will need to differentiate between this scenario and scenario where chunk read is timing out.

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


With regards,
Apache Git Services

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