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
x-distributed version checks / diagnostic. #595
Comments
Agreed. This could be implemented in the following steps:
|
jreback
added a commit
to jreback/distributed
that referenced
this issue
Oct 19, 2016
…oning information closes dask#595
jreback
added a commit
to jreback/distributed
that referenced
this issue
Oct 19, 2016
…oning information closes dask#595
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Having mismatched version across the cluster can be hard to detect and cause very odd error reports.
a function to give a snapshot of the versions of various required packages that are used in pieces of the system would be useful. IOW, we have scheduler, workers, and the user environment.
This would be a first step towards a validation of the environments. IOW, it is very important that we have the same versions of
distributed
running on the workers & the user env. For some operations it is imperative thatdask
match (or at least be compatible). I imagine othercloudpickle
&msgpack-python
should be compatible as well.So I would envision a
client.get_versions()
which could return data on each worker, the user environment and the scheduler environment. (maybe aDataFrame
of results).At the very least this would be a nice diagnostic. Furthermore maybe then the scheduler could provide a warning if mismatches in versions exist.
This would be somewhat linked with #300 as full-fledged environments would also need tools to introspect the remote environments.
The text was updated successfully, but these errors were encountered: