Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
Description
When cluster is unavailable, router -> namenode communication will only retry once without any time interval, that is not reasonable.
For example, in my company, which has several hdfs clusters with more than 1000 nodes, we have encountered this problem. In some cases, the cluster becomes unavailable briefly for about 10 or 30 seconds, at the same time, almost all rpc requests to router failed because router only retry once without time interval.
It's better for us to enhance the router retry strategy, to retry **communicate with NN using configurable time interval and max retry times.
Attachments
Issue Links
- links to