Uploaded image for project: 'HBase'
  1. HBase
  2. HBASE-13453

Master should not bind to region server ports

    XMLWordPrintableJSON

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Critical
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 1.1.0, 2.0.0
    • Component/s: None
    • Labels:
      None
    • Release Note:
      Hide
      In 1.0.x, master by default binds to the region server ports (both rpc and info). This change brings back the usage of old master rpc and info ports in 1.1+ and master (2.0) branches. The motivation for this change is to ease the life of the user so that he does not need to do anything to bring up a RS on the same host and also to make the migration from 0.98 to 1.1 hassle free. However, the users going from 1.0 to 1.1 would see the change in the master ports.
      Show
      In 1.0.x, master by default binds to the region server ports (both rpc and info). This change brings back the usage of old master rpc and info ports in 1.1+ and master (2.0) branches. The motivation for this change is to ease the life of the user so that he does not need to do anything to bring up a RS on the same host and also to make the migration from 0.98 to 1.1 hassle free. However, the users going from 1.0 to 1.1 would see the change in the master ports.

      Description

      In 1.0, master by default binds to the region server ports (rpc and info). We have done it so thinking that in the long term, master and meta co-location will be default, and we can merge the master and region server as a single daemon.

      Over at HBASE-11165, if the conclusion end up being that meta will not be colocated at all, then master hosting a region server will just become an implementation detail. Stack says that we might never allow master to host regions.

      Now, we are stuck in a state where we have made master bind to RS ports in 1.0, which might create some confusion (and frustration) for small cluster users who traditionally used to host a master and a region server on the same node.

      I think we should undo this in 1.1 and use the previous master ports (16000) and not bind to 16030, so that the user does not need to do anything to bring up a RS on the same host. At least users going from 0.98 -> 1.1 will not take a hit. Users going from 1.0 -> 1.1 will see changed default ports.

        Attachments

        1. HBASE-13453.patch
          4 kB
          Srikanth Srungarapu
        2. HBASE-13453.patch
          3 kB
          Srikanth Srungarapu
        3. 34111-2.txt
          3 kB
          Devaraj Das
        There are no Sub-Tasks for this issue.

          Activity

            People

            • Assignee:
              srikanth235 Srikanth Srungarapu
              Reporter:
              enis Enis Soztutar
            • Votes:
              0 Vote for this issue
              Watchers:
              12 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: