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

Don't consider GPU-based nodes in databricks_node_type data source until explicitly requested #1978

Merged
merged 1 commit into from
Feb 3, 2023

Conversation

alexott
Copy link
Contributor

@alexott alexott commented Feb 3, 2023

This fixes a situation when nodes with GPU were included into consideration even if there was no request to consider them - as result. For example, instead of expected m5d.2xlarge the g4dn.2xlarge was selected.

@alexott alexott requested review from a team February 3, 2023 12:01
@codecov-commenter
Copy link

Codecov Report

Merging #1978 (85f9f63) into master (ea3acc0) will decrease coverage by 0.02%.
The diff coverage is 100.00%.

Additional details and impacted files

Impacted file tree graph

@@            Coverage Diff             @@
##           master    #1978      +/-   ##
==========================================
- Coverage   90.36%   90.34%   -0.02%     
==========================================
  Files         146      146              
  Lines       11901    11901              
==========================================
- Hits        10754    10752       -2     
- Misses        741      742       +1     
- Partials      406      407       +1     
Impacted Files Coverage Δ
clusters/data_node_type.go 91.95% <100.00%> (-2.30%) ⬇️

@alexott alexott force-pushed the node_type-no-gpu-request-fix branch from 85f9f63 to 864a669 Compare February 3, 2023 12:16
@alexott alexott mentioned this pull request Feb 3, 2023
@nfx nfx merged commit 0f3d2ec into master Feb 3, 2023
@nfx nfx deleted the node_type-no-gpu-request-fix branch February 3, 2023 15:46
nfx added a commit that referenced this pull request Feb 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants