MingXiangLi commented on PR #5170: URL: https://github.com/apache/hadoop/pull/5170#issuecomment-1333372902
The BLOCK_POOl level lock is to protect replica consistency for FsDataSetImpl when read or write operating happend at same time. > forbid refresh() when ReplicaCachingGetSpaceUsed #init() at first time，it will cause the value of dfsUsage to be 0 until the next time refresh(). For example we can use df command instead at first time or other way. On my side It's less risky to change ReplicaCachingGetSpaceUsed logic than remove the write lock. Or we can further discussion to make sure no case will lead to consistency problem if we remove write lock. -- 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: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
