Uploaded image for project: 'CDAP'
  1. CDAP
  2. CDAP-7192

Add the ability to specify a Advertise Address and Bind Address on CDAP Services

    Details

    • Type: Improvement
    • Status: Resolved
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 3.5.0
    • Fix Version/s: 4.0.0, 3.6.0, 3.5.1
    • Component/s: CDAP Apps
    • Labels:
    • Release Notes:
      Hide
      Added the ability to specify an announce address and port for the appfabric and dataset services. Deprecated the properties app.bind.address and dataset.service.bind.address, replacing them with master.services.bind.address as the bind address for master services. Added the properties master.services.announce.address, app.announce.port, and dataset.service.announce.port for use as announce addresses that are different from the bind address.
      Show
      Added the ability to specify an announce address and port for the appfabric and dataset services. Deprecated the properties app.bind.address and dataset.service.bind.address, replacing them with master.services.bind.address as the bind address for master services. Added the properties master.services.announce.address, app.announce.port, and dataset.service.announce.port for use as announce addresses that are different from the bind address.
    • Rank:
      1|hzzl8n:

      Description

      When CDAP services are deployed to yarn / zookeeper we need to ability to configure a <service>.bind.address and <service>.advertise.address.

      Current problem.
      CDAP services leveraging Netty need to have a bind.address of 0.0.0.0. This allows any requestor to access the service as long as they are communicating with the bind.port. Services such as the dataset.service do not allow overriding this value in the cdap-site.xml.

      Also, when these services get registered in Zookeeper we need to specify the FQDN of the Server or Servers running CDAP services. Registering the FQDN with Zookeeper allows us to route traffic correctly over our F5 Big IP layer, and ultimately to our Docker containers.

      One of our developers has started making modifications to these services to test out this functionality. Attached is a patch of his current changes. After applying the path we are able to configure both the bind.address and advertise.address for the dataset.service. However, the appfabric.service does not respect the added advertise.address.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                shankar Shankar Selvam
                Reporter:
                tfokken Troy Fokken
              • Votes:
                0 Vote for this issue
                Watchers:
                4 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: