Skip to content

Reject conflicting KubeCluster options when using a custom cluster spec - #979

Open
ajiteshbankulaa wants to merge 2 commits into
dask:mainfrom
ajiteshbankulaa:fix-882-custom-spec-options
Open

ajiteshbankulaa wants to merge 2 commits into
dask:mainfrom
ajiteshbankulaa:fix-882-custom-spec-options

Conversation

@ajiteshbankulaa

Copy link
Copy Markdown

Description

When custom_cluster_spec is provided, KubeCluster uses that spec only. Even though Constructor options such as idle_timeout were still accepted, they had no effect. For example, passing idle_timeout=30 alongside a custom spec with idleTimeout: 0 would leave the timeout at 0.

This change I made it such that it raises a ValueError when a custom spec is combined with options that belong in the spec. The error tells users to set those values in the custom spec or pass them to make_cluster_spec(). It also covers custom specs supplied through Dask configuration.

I updated the existing custom spec tests to put their options in make_cluster_spec() and added tests for the conflicting arguments.

This addresses the ignored arguments discussed in #882. The missing key timer exception was addressed separately in #884.

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.

1 participant