[PR] HDFS-17769. Allows client to actively retry to Active NameNode when the Observer NameNode is too far behind client state id. [hadoop]

[via GitHub]

gyz-web opened a new pull request, #7602:
URL: https://github.com/apache/hadoop/pull/7602

     When we use Router to forward read requests to the observer, if the 
cluster experiences heavy write workloads, Observer nodes may fail to keep pace 
with edit log synchronization, even if the dfs.ha.tail-edits.in-progress 
parameter is configured, it may still occur.This triggers RetriableException: 
Observer Node is too far behind errors. Especially when the client 
ipc.client.ping parameter is set to true, it will strive to wait and constantly 
retry, which can cause the business to be unable to obtain the desired data 
timely. We should consider having the active namenode handle this at this time.
   
   Here are our some errors and repair verification:
   
   1.The stateid of the observer is too far behind the active:
   
![图片1](https://github.com/user-attachments/assets/7e9df660-e67d-4aaa-878a-25e083afaa0d)
   
   2.RetriableException:
   
![图片2](https://github.com/user-attachments/assets/a691d613-c1b9-4c81-9282-cd10fe337029)
   
   
   3.repair verification:
   
![图片3](https://github.com/user-attachments/assets/ab235d1d-95ce-481f-9ee8-7220db9d8897)
   


-- 
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