You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "ramkrishna.s.vasudevan (Created) (JIRA)" <ji...@apache.org> on 2012/04/20 07:45:37 UTC

[jira] [Created] (HBASE-5839) Backup master not starting up due to Bind Exception while starting HttpServer

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

        

[jira] [Commented] (HBASE-5839) Backup master not starting up due to Bind Exception while starting HttpServer

Posted by "Uma Maheswara Rao G (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (HBASE-5839) Backup master not starting up due to Bind Exception while starting HttpServer

Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-5839:
---------------------------------

    Fix Version/s:     (was: 0.94.1)
                   0.94.2

Moving out of 0.94.1
                
> 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.2
>
>
> 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

        

[jira] [Updated] (HBASE-5839) Backup master not starting up due to Bind Exception while starting HttpServer

Posted by "Lars Hofhansl (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-5839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Lars Hofhansl updated HBASE-5839:
---------------------------------

    Fix Version/s:     (was: 0.94.2)

I don't think we have any short term actionable items here. Moving out of 0.94
                
> 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
>
>
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira