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

info: output Dask-related information #163

Open
tiborsimko opened this issue Nov 1, 2024 · 0 comments · May be fixed by #164
Open

info: output Dask-related information #163

tiborsimko opened this issue Nov 1, 2024 · 0 comments · May be fixed by #164

Comments

@tiborsimko
Copy link
Member

Current behaviour

After Dask workflow support has been added to REANA, the Python client info command replies with some Dask-related information to the user, whilst the Go client does not:

$ rc info | grep -i dask
The number of Dask workers created by default: 2
The amount of memory used by default by a single Dask worker: 2Gi
The maximum memory limit for Dask clusters created by users: 16Gi
The maximum amount of memory that users can ask for the single Dask worker: 8Gi
Dask workflows allowed in the cluster: True

$ rcg info | grep -i dask

Expected behaviour

REANA Go client should also output the Dask-related information, on parity with what the Python client does.

@tiborsimko tiborsimko added this to 0.95.0 Nov 1, 2024
@tiborsimko tiborsimko moved this to Ready for work in 0.95.0 Nov 1, 2024
Alputer added a commit to Alputer/reana-client-go that referenced this issue Nov 11, 2024
Alputer added a commit to Alputer/reana-client-go that referenced this issue Nov 11, 2024
Alputer added a commit to Alputer/reana-client-go that referenced this issue Nov 20, 2024
Alputer added a commit to Alputer/reana-client-go that referenced this issue Nov 20, 2024
Alputer added a commit to Alputer/reana-client-go that referenced this issue Nov 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: In review
Development

Successfully merging a pull request may close this issue.

1 participant