You are viewing a plain text version of this content. The canonical link for it is here.
Posted to common-issues@hadoop.apache.org by GitBox <gi...@apache.org> on 2019/08/27 08:36:35 UTC

[GitHub] [hadoop] bshashikant commented on issue #1349: HDDS-2026. Overlapping chunk region cannot be read concurrently

bshashikant commented on issue #1349: HDDS-2026. Overlapping chunk region cannot be read concurrently
URL: https://github.com/apache/hadoop/pull/1349#issuecomment-525200958
 
 
   Thanks @adoroszlai for working on this. The locking logic seems good to me.
   But in Ozone world, a chunk once written is immutable , and hence we might not need the lock at all
   while reading a chunk. 
   
   @anuengineer @elek @mukul1987 what do you think?
   There is also a race condition which exists in the system where a chunk might get deleted by BlockDeleting service in Datanode while readChunk is happening which is where i think we need to have synchronization on a container level (not precisely at the chunk level) for closed containers.

----------------------------------------------------------------
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: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org