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

init_blocks needs to be 0 for kubernetes provider #237

Closed
ZhuozhaoLi opened this issue Sep 1, 2020 · 0 comments · Fixed by #468
Closed

init_blocks needs to be 0 for kubernetes provider #237

ZhuozhaoLi opened this issue Sep 1, 2020 · 0 comments · Fixed by #468
Assignees
Labels
bug Something isn't working

Comments

@ZhuozhaoLi
Copy link
Contributor

ZhuozhaoLi commented Sep 1, 2020

When init_blocks is not set to 0 with kubernetes providers, funcx-endpoint raises the following exception:

2020-09-01 20:28:46.249 interchange:254 [ERROR]  Caught exception
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/funcx_endpoint/executors/high_throughput/interchange.py", line 252, in __init__
    self.load_config()
  File "/usr/local/lib/python3.6/site-packages/funcx_endpoint/executors/high_throughput/interchange.py", line 301, in load_config
    self.scale_out(self.config.provider.init_blocks)
  File "/usr/local/lib/python3.6/site-packages/funcx_endpoint/executors/high_throughput/interchange.py", line 802, in scale_out
    internal_block = self.config.provider.submit(launch_cmd, 1)
TypeError: submit() missing 1 required positional argument: 'task_type'

It should either raise a more informative exception to the user or ignore init_blocks for k8s.

@ZhuozhaoLi ZhuozhaoLi self-assigned this Sep 1, 2020
@ZhuozhaoLi ZhuozhaoLi added the bug Something isn't working label Sep 1, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant