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

Explore possibilities to lower in-use IP address quota footprint. #19465

Closed
kennknowles opened this issue Jun 4, 2022 · 9 comments
Closed

Explore possibilities to lower in-use IP address quota footprint. #19465

kennknowles opened this issue Jun 4, 2022 · 9 comments

Comments

@kennknowles
Copy link
Member

 


java.lang.RuntimeException: Workflow failed. Causes: Project apache-beam-testing has insufficient quota(s)
to execute this workflow with 1 instances in region us-central1. Quota summary (required/available):
1/11743 instances, 1/170 CPUs, 250/278399 disk GB, 0/4046 SSD disk GB, 1/188 instance groups, 1/188
managed instance groups, 1/126 instance templates, 1/0 in-use IP addresses.

 

Sample jobs:
https://builds.apache.org/job/beam_PostCommit_Java11_ValidatesRunner_Dataflow/440/testReport/junit/org.apache.beam.sdk.testing/PAssertTest/testGlobalWindowContainsInAnyOrder/

https://builds.apache.org/job/beam_PostCommit_Java_ValidatesRunner_Dataflow_PR/67/testReport/junit/org.apache.beam.sdk.transforms/ViewTest/testEmptyIterableSideInput/

 

Imported from Jira BEAM-7410. Original Jira may contain additional context.
Reported by: Ardagan.

@apilloud
Copy link
Member

Issue ongoing: https://ci-beam.apache.org/job/beam_PreCommit_Java_Examples_Dataflow_Phrase/809/testReport/junit/org.apache.beam.examples/WindowedWordCountIT/testWindowedWordCountInBatchDynamicSharding/

java.lang.RuntimeException: Workflow failed. Causes: Project apache-beam-testing has insufficient quota(s) to execute this workflow with 1 instances in region us-central1. Quota summary (required/available): 1/38755 instances, 2/1265 CPUs, 25/330889 disk GB, 0/553 SSD disk GB, 1/283 instance groups, 1/286 managed instance groups, 1/402 instance templates, 1/0 in-use IP addresses.

@damondouglas
Copy link
Contributor

.add-labels beam-fixit

@damondouglas
Copy link
Contributor

Communicated assessment/recommendation internally.

@damondouglas
Copy link
Contributor

.take-issue

@aaltay
Copy link
Member

aaltay commented Jan 13, 2023

Is this still an issue worth addressing soon? Are we running into infra issues for issues related to this quota?

@damondouglas
Copy link
Contributor

Please see personal communication.

@damondouglas
Copy link
Contributor

@kennknowles Unassigned this issue as it the fix requires access to the jenkins environment for efficient debugging and testing that I do not have at this time.

@Abacn
Copy link
Contributor

Abacn commented Jul 18, 2023

Each Jenkins node uses a static IP address, so 16 addresses in total. This is required to connect with the Jenkins master that is managed by Apache Infra. From gcp console there are actually two complete set of Jenkins node, one in use (apache-ci-beam-jenkins-nodes) and another are long stopped (apache-beam-jenkins-jnlp-group). The former was created on Jun 10, 2020 and latter was created on Apr 9, 2019. Likely the latter was no longer in use and resources could be released.

@Abacn
Copy link
Contributor

Abacn commented Jul 18, 2023

deleted 17 instances and released these static IP address. This should suffice to resolve the quota issue.

IP address quota footprint would be further decreased once we migrate to k8s based github action runner, and finally teardown jenkins

close this issue for now

@Abacn Abacn closed this as completed Jul 18, 2023
@github-actions github-actions bot added this to the 2.50.0 Release milestone Jul 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

5 participants