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.

Sign up for GitHub

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

Jump to bottom

[BUG] AutoTuner should not recommend jobs with 1 worker nodes in Dataproc #1521

Open
parthosa opened this issue Jan 31, 2025 · 0 comments · May be fixed by #1537
Open

[BUG] AutoTuner should not recommend jobs with 1 worker nodes in Dataproc #1521

parthosa opened this issue Jan 31, 2025 · 0 comments · May be fixed by #1537
Assignees
@parthosa
Labels
autotuner bug Something isn't working core_tools Scope the core module (scala)

Comments

@parthosa
Copy link
Collaborator

Currently, the Qualification AutoTuner recommends using 1 x n1-standard-16 instance for a CPU job with 8 cores and 2 instances. However, Dataproc does not support clusters with only 1 worker node.

We should enforce a lower bound and avoid qualifying such jobs.
@parthosa parthosa added ? - Needs Triage bug Something isn't working core_tools Scope the core module (scala) labels Jan 31, 2025
@parthosa parthosa linked a pull request Feb 7, 2025 that will close this issue
Draft
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@parthosa parthosa

Labels
autotuner bug Something isn't working core_tools Scope the core module (scala)
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Handle invalid cluster recommendation for Dataproc parthosa/spark-rapids-tools
2 participants
@parthosa @amahussein