Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[FLINK-33246][tests] Add AutoRescalingITCase #23510

Closed

Conversation

StefanRRichter
Copy link
Contributor

What is the purpose of the change

Adds AutoRescalingITCase, an adapted rescaling IT case that uses checkpointing and changing resource requirements to trigger rescaling.

Does this pull request potentially affect one of the following parts:

  • Dependencies (does it add or upgrade a dependency): (no)
  • The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
  • The serializers: (no)
  • The runtime per-record code paths (performance sensitive): (no)
  • Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
  • The S3 file system connector: (no)

Documentation

  • Does this pull request introduce a new feature? (no)
  • If yes, how is the feature documented? (not applicable)

@flinkbot
Copy link
Collaborator

flinkbot commented Oct 11, 2023

CI report:

Bot commands The @flinkbot bot supports the following commands:
  • @flinkbot run azure re-run the last Azure build

builder.setParallelismForJobVertex(vertex.getID(), parallelism2, parallelism2);
}

restClusterClient.updateJobResourceRequirements(jobID, builder.build()).join();
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIRC, this call doesn't wait for the requirements to be satisfied.
Should we wait after this call, that the actual DoP is actually what we want?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was looking into this and think it is not needed for this test because the test job will only start completing after it restarted from the rescale, so we can be sure that the rescaling happened first.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Relying on that condition seems a bit fragile to me and makes it more difficult to understand.

  • there were no restarts; they are disabled here, but I'm not sure if the restarts are disabled in every tests, and whether they will stay as such.
  • the DoP might change if some TM is slow to start; the scheduler will first schedule with lower DoP, and once TM is up, will rescale to full DoP. That happened in some tests previously

@StefanRRichter StefanRRichter force-pushed the srichter-FLINK-33246 branch 2 times, most recently from 882f41e to b0bb6d6 Compare October 12, 2023 12:06
@StefanRRichter
Copy link
Contributor Author

Closing in favor of #23591

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants