haiyang1987 commented on PR #6176: URL: https://github.com/apache/hadoop/pull/6176#issuecomment-1772160261
I try to implement this based on the timeout mechanism solution. However, there is a case where I have some questions, such as: - t1 time: Block1 on DN1 is choosed to be added to ExcessRedundancyMap. - t2 time: DN1 heartbeat gets Invalidates command. - t3 time: Due to a serious accumulationin DN1 async deletion queue, the replica might not be deleted for a prolonged period. The question here is how the current NN can define a reasonable timeframe to determine whether Block1 corresponding to DN1 in ExcessRedundancyMap has timed out. Currently, I haven't think of a particularly good way to define this. Hi @Hexiaoqiao @ZanderXu @zhangshuyan0 excuse me, do you have any suggestions for this case? look forward to your feedback, Thanks~ -- 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
