-
-
Notifications
You must be signed in to change notification settings - Fork 718
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
Fix UCX scrub config logging #4850
Conversation
Thanks @pentschev . I'll merge after passing |
Is there anything we can put into a test here? |
You could put in an invalid UCX config option then check debug output. |
Not really, because we don't let users specify those manually and the current code will never encounter a condition where it can fail. We could do a mock test, but I don't think it's worth the time to be honest, we might just wipe that check out instead as in its current state it will never fail (unless there's a change in UCX). |
I'm not familiar with the UCX code and trust your judgment. If this is fine without a test, go ahead. |
Thank you for the comments and review @fjetter |
Thanks all for the reviews! |
Support for setting UCX global options was dropped in dask/distributed#4850, as the conflict of Dask configs and UCX configs can be dangerous since both used to live in the same namespace. Setting global UCX options can still be done via environment variables, such as `UCX_*`, and is the preferred method now.
Support for setting UCX global options was dropped in dask/distributed#4850, as the conflict of Dask configs and UCX configs can be dangerous since both used to live in the same namespace. Setting global UCX options can still be done via environment variables, such as `UCX_*`, and is the preferred method now. Fixes #627 Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Mads R. B. Kristensen (https://github.com/madsbk) URL: #738
I believe this check was originally intended to work as a map from
DASK_UCX__*
to the actualUCX_*
configurations. Since the original implementation the UCX configurations in Dask have evolved to aliases, so the mapping doesn't match. However, theoptions
variable is what is passed to UCX, so we should verify that we're not setting variables that don't match those that UCX exposes.