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 2022/09/01 08:42:43 UTC

[GitHub] [hadoop] ayushtkn commented on pull request #4813: HDFS-16748. DFSClient should uniquely identify writing files by namespace id and iNodeId via RBF

ayushtkn commented on PR #4813:
URL: https://github.com/apache/hadoop/pull/4813#issuecomment-1233950469

   >even if one inode is overwrited by another one with same id, it will send renewLease to all namenode, and can not lose lease for client, right? P
   
   Just thinking, if the second file which was on top, which overwrote the previous entry gets closed, then there would be no entry & in that case renewLease will not be triggered only for the entry which got overwritten, even without the previous patch? Am I missing something...


-- 
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-unsubscribe@hadoop.apache.org

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


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