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

Service could expose blob server port mismatched with JM Container

Attach filesAttach ScreenshotVotersWatch issueWatchersCreate sub-taskLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    Description

      The Service would always expose 6124 port if it should expose that port, and while building ServicePort we do not explicitly specify a target port, so the target port would always be 6124 too.

      // From ServiceDecorator.java
      
      servicePorts.add(getServicePort(
       getPortName(BlobServerOptions.PORT.key()),
       Constants.BLOB_SERVER_PORT));
      
      private ServicePort getServicePort(String name, int port) {
         return new ServicePortBuilder()
            .withName(name)
            .withPort(port)
            .build();
      }
      
      
      

       

      meanwhile, the Container of the JM would expose the blob server port which is configured in the Flink Configuration,

      // From FlinkMasterDeploymentDecorator.java
      
      final int blobServerPort = KubernetesUtils.parsePort(flinkConfig, BlobServerOptions.PORT);
      
      ...
      
      final Container container = createJobManagerContainer(flinkConfig, mainClass, hasLogback, hasLog4j, blobServerPort);
      

       

      so there is a risk that in non-HA mode the TM could not execute Task due to dependencies fetching failure if the Service exposes a blob server port which is different from the JM Container when one configures the blob server port with a value different from 6124.

       

      Attachments

        Issue Links

        Activity

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

          People

            felixzheng Canbin Zheng
            felixzheng Canbin Zheng
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Time Tracking

                Estimated:
                Original Estimate - Not Specified
                Not Specified
                Remaining:
                Remaining Estimate - 0h
                0h
                Logged:
                Time Spent - 20m
                20m

                Slack

                  Issue deployment