Uploaded image for project: 'Flink'
  1. Flink
  2. FLINK-2769

Web dashboard port not configurable on client side

Agile BoardRank to TopRank to BottomAttach filesAttach ScreenshotBulk Copy AttachmentsBulk Move AttachmentsVotersStop watchingWatchersCreate sub-taskConvert to sub-taskLinkCloneLabelsUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Critical
    • Resolution: Fixed
    • 0.10.0
    • 0.10.0, 1.0.0
    • Runtime / Web Frontend
    • None

    Description

      The new web dashboard port configuration only affects the server side, but not the client side.

      To reproduce set in flink-conf.yaml:

      jobmanager.web.port: 9091
      jobmanager.new-web-frontend: true
      

      Run

      $ bin/start-cluster.sh
      

      You can browse to http://localhost:9091, but you won't see any data from the job manager. Requests to http://localhost:9091/overview etc. work as expected, but the client side JavaScript is running requests against http://localhost:8081.

      The problem is that flink-runtime-web/web-dashboard/app/scripts/index.coffee hard codes:

      .value 'flinkConfig', {
        jobServer: 'http://localhost:8081'
      }
      

      which is picked up by all generated scripts.

      This needs to be configurable for both standalone mode but especially for recovery mode. This was a major pain point for me today, because I was working on the dashboard and thought that my changes were wrong.

      In general, we need to add more tests to the new dashboard, which should soon replace the old one imo.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            uce Ufuk Celebi
            uce Ufuk Celebi
            Votes:
            0 Vote for this issue
            Watchers:
            4 Stop watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment