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

Rethink the necessity of the k8s internal Service even in non-HA mode

    XMLWordPrintableJSON

Details

    Description

      In non-HA mode, k8s will create internal service that directs the communication from TaskManagers Pod to JobManager Pod, and TM Pods could re-register to the new JM Pod once a JM Pod failover occurs.

      However recently I do an experiment and find a problem that k8s will first create new TM pods and then destory old TM pods after a period of time once JM Pod failover (note: new JM podIP has changed), then job will be reschedule by JM on new TM pods, it means new TM has been registered to JM. 

      During this process, internal service is active all the time, but I think it is not necessary that keep this internal service, In other words, wo can weed out internal service and use JM podIP for TM pods communication with JM pod, In this case, it be consistent with HA mode.

      Finally,related experiments is in attached (k8s internal service.pdf).

      Attachments

        1. k8s internal service.pdf
          453 kB
          Ruguo Yu
        2. k8s internal service - v2.pdf
          1.12 MB
          Ruguo Yu
        3. k8s internal service - in english.pdf
          1.30 MB
          Ruguo Yu

        Issue Links

          Activity

            People

              Unassigned Unassigned
              jiang7chengzitc Ruguo Yu
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: