Hexiaoqiao commented on PR #5583: URL: https://github.com/apache/hadoop/pull/5583#issuecomment-1519894678
Got it. Thanks for the additional information. IIUC, the root cause includes, a. Standby postpone process request (BRD) from DataNode due to some reason, b. Active and Standby failover, c. Replica's timestamp has upgraded (because append or recovery lease or other reason), this three conditions have to intersect, right? I agree ZanderXu's proposal that we should not put the replica to `corruptReplicas` set if there was another newest replica has reported already, or one stale replica should ignore directly. -- 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
