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

Do not change min resource requirements when rescaling for adaptive scheduler

    XMLWordPrintableJSON

Details

    Description

      when applying the rescale api to change parallelism we should not change the min parallelism.
      The problem currently is that if we cannot aquire the new resources within jobmanager.adaptive-scheduler.resource-wait-timeout the job will completely fail

      The jobmanager.adaptive-scheduler.resource-stabilization-timeout still allows us to wait for quite long if necessary to get the target parallelism but failing completely because of the wait timeout seems very unfortunate

      It's best to keep the min resources unchanged and let the adaptive scheduler take care of the parallelism changes together with the timeout settings.

      Attachments

        Issue Links

          Activity

            People

              gyfora Gyula Fora
              gyfora Gyula Fora
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: