[
https://issues.apache.org/jira/browse/HBASE-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258044#comment-13258044
]
Uma Maheswara Rao G commented on HBASE-5839:
--------------------------------------------
bq. Even before that the Data Xceviers threads (IPC handlers) are started and
they are started at random port.
DataXceiver server will listen on fixed port, 50010.
Clients only will bind to random ports for short term. Even I have seen this
situations some times in my clusters.
We followed to set the fixed ports of servers at range of ~65000. It may just
reduce the probability of clients to binding on the same ports. As per our
observations, that random ports did not reach to this level. Not sure, is there
any specific range for random ports.
This problem may be unavoidable problem. Restart servers only the option. Let's
see if anyone has some better idea to avoid this situation.
> Backup master not starting up due to Bind Exception while starting HttpServer
> -----------------------------------------------------------------------------
>
> Key: HBASE-5839
> URL: https://issues.apache.org/jira/browse/HBASE-5839
> Project: HBase
> Issue Type: Bug
> Reporter: ramkrishna.s.vasudevan
> Fix For: 0.96.0, 0.94.1
>
>
> Backup master tries to bind to the info port 60010.
> This is done once the back up master becomes active. Even before that the
> Data Xceviers threads (IPC handlers) are started and they are started at
> random port. If already 60010 is used then when standby master comes up then
> it fails due to bind exception.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
