-NN uses up all ports (java.net.BindException: Cannot assign requested address)
Jianhui Zhang 2012-10-09, 23:17
We've seen this the second time. The JT had this error:
2012-10-08 11:44:03,928 WARN org.apache.hadoop.hdfs.DFSClient: Problem
renewing lease for DFSClient_1416124356
java.io.IOException: Call to nn-virtual.x.y.z/18.104.22.168:8020 failed on local
exception: java.net.BindException: Cannot assign requested address
at $Proxy5.renewLease(Unknown Source)
and it has been trying to reconnect to the NN:
2012-10-08 11:44:03,927 INFO org.apache.hadoop.ipc.Client: Retrying connect
to server: nn-virtual.x.y.z/22.214.171.124:8020. Already tried 9 time(s).
The problem persisted. Some of our MR jobs were successful, some failed
with the error above....
So I listed out all the local addresses and got about 24K of them. The
We are not reaching the limit, but very close. What's strange is: almost
all of the local ports are used by the NN process. There might be some
holes in the list, but overall, it seems using up all the ephemeral ports
available in the range.
Right now, I strongly suspect that "Cannot assign requested address" is due
to lack of ports - although I'm not 100% sure since the ephemeral ports
change all the time.
Here are my questions:
1. Has anybody seen this before? Any pointers would be appreciated.
2. We are using a virtual IP for the NN. Could it be related to the
Thanks for your help,