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

In Ambari integrated distributed cluster router bind address should point to the actual host name

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Won't Fix
    • Affects Version/s: 4.0.0, 3.6.0
    • Fix Version/s: None
    • Component/s: Ambari Service, Router
    • Labels:
    • Rank:
      1|hzzqfr:

      Description

      In a distributed Ambari managed cluster, CDAP installed and CDAP services running on a different nodes.
      Ambari configuraton provides:
      router.bind.address = 0.0.0.0
      router.bind.port = 11015

      Router runs on host1 and cdap-cli.sh works correctly on it.
      [root@host1 ~]# cdap-cli.sh
      Successfully connected to CDAP instance at http://host1:11015/default
      cdap (http://host1:11015/namespace:default)>

      Attempt to connect from other node (host2) failed:
      [root@host2 ~]# cdap-cli.sh
      CDAP instance at 'http://hohst2:11015/default' could not be reached: Connection refused (Connection refused)
      Specify the CDAP instance URI with the -u command line argument.

      After change router.bind.address to point to the actual hostname problem gone.
      Needs to be fixed.

        Attachments

          Activity

            People

            • Assignee:
              nitin Nitin Motgi
              Reporter:
              leonid Leonid Fedotov
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: