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

Dask clusters issues #2945

Closed
10 tasks done
sanderegg opened this issue Apr 4, 2022 · 1 comment · Fixed by #4033, #4022 or #4036
Closed
10 tasks done

Dask clusters issues #2945

sanderegg opened this issue Apr 4, 2022 · 1 comment · Fixed by #4033, #4022 or #4036
Assignees
Labels
a:director-v2 issue related with the director-v2 service a:frontend issue affecting the front-end (area group) a:webserver issue related to the webserver service
Milestone

Comments

@sanderegg
Copy link
Member

sanderegg commented Apr 4, 2022

Frontend:

general pipeline

  • empty pipeline should not be runnable (shows are you sure to run dialog indefinitely)

Cluster preferences:

  • selected cluster does not show members
  • after selecting default cluster, it is not possible to select other clusters anymore
  • if the cluster already exists, then the ping call should use POST /clusters/{c_id}:ping instead of POST /clusters:ping with ********* as password
  • When a cluster is added (and works correctly) and later restarted (restarting the host or restarting the gateway/cluster), in the case where we have exactly the same credentials, the ping test always shows red. When going into preferences, editing the cluster and testing it (without updating any informations), the connection will work. But It doesn't solve the bug and the test will fail everywhere else.

Resource manager

  • it takes a long time to show the cluster details (although /details returns in <30ms) It would be nice to show something is going on at least
  • when there is data to show why is it taking so much time?
  • alignment of the pies and pies titles is weird
  • should we maybe use something more compact? like bars? and put them aligned in a table?
  • some ideas:
    • remove the title "C-0" ?
    • move the connection status on the same row like the cluster selection dropbox?
    • show a worker icon instead of the worker name (maybe keep the name in the hover)

Backend:

  • Ping an unconnected cluster times-out only after 30s?
  • Ping a cluster with wrong port shows Internal server error
  • deleting a cluster fails as soon as the cluster was used in a computational run (the comp_runs table uses the cluster id as a foreign key and does not allow doing this)
  • add cluster, restart the cluster, then the connection ping fails
  • dask-worker backend metrics are only showing the dask-worker process metrics
  • removing members from cluster using the frontend doesn't work
@sanderegg
Copy link
Member Author

closing as out of date and mostly fixed. will be replaced by a new entry that is up to date

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
a:director-v2 issue related with the director-v2 service a:frontend issue affecting the front-end (area group) a:webserver issue related to the webserver service
Projects
None yet
2 participants