lyft / lyft/flinkk8soperator

Scale Up Integration Test Fix

Open
#278 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
581
Forks
153
PR merge metrics
No merged PRs in 30d

Description

## overview
Scale up test is being commented out to get integration tests working on github actions. The issue is that github hosted runners only allow 8gb memory and 2 cpu by default. The scale up test requires 2 flink clusters to run simultaneously, one with 2 tm's with 2 task slots each and one with 1 tm with 2 task slots. Other tests only require 1 tm per flink cluster and have been squeezed into the github hosted runner by decreasing parallelism during testing.

To get this test to run, we'll need to use larger github runners which is currently in beta.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Inspect the GitHub Actions workflow where the scale up integration test is commented out, and review how other tests reduce parallelism to fit the hosted runner. Confirm the larger runner option and its resource limits, then run the scale up test with two Flink clusters and verify the integration suite passes.

Written by the indexing model from the issue text.

Assessment

Tech stack
github-actions
Domain
ci-cd, testing
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.