{"action":"created","issue":{"url":"https://api.github.com/repos/dask/distributed/issues/1951","repository_url":"https://api.github.com/repos/dask/distributed","labels_url":"https://api.github.com/repos/dask/distributed/issues/1951/labels{/name}","comments_url":"https://api.github.com/repos/dask/distributed/issues/1951/comments","events_url":"https://api.github.com/repos/dask/distributed/issues/1951/events","html_url":"https://github.com/dask/distributed/issues/1951","id":319676397,"number":1951,"title":"Distributed's Adaptive's Scheduler `retire_workers` and Cluster `scale_down`","user":{"login":"jakirkham","id":3019665,"avatar_url":"https://avatars1.githubusercontent.com/u/3019665?v=4","gravatar_id":"","url":"https://api.github.com/users/jakirkham","html_url":"https://github.com/jakirkham","followers_url":"https://api.github.com/users/jakirkham/followers","following_url":"https://api.github.com/users/jakirkham/following{/other_user}","gists_url":"https://api.github.com/users/jakirkham/gists{/gist_id}","starred_url":"https://api.github.com/users/jakirkham/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jakirkham/subscriptions","organizations_url":"https://api.github.com/users/jakirkham/orgs","repos_url":"https://api.github.com/users/jakirkham/repos","events_url":"https://api.github.com/users/jakirkham/events{/privacy}","received_events_url":"https://api.github.com/users/jakirkham/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-02T19:09:23Z","updated_at":"2018-05-02T20:10:53Z","closed_at":null,"author_association":"OWNER","body":"It appears that [Distributed's Adaptive tells the Scheduler to `retire_workers` and then `scale_down` the Cluster]( https://github.com/dask/distributed/blob/1.21.7/distributed/deploy/adaptive.py#L230-L235 ). Is there a reason both of these operations are needed? Also what does this mean for downstream libraries inheriting from Distributed's Adaptive or Distributed's Cluster?\r\n\r\nxref: https://github.com/dask/dask-drmaa/issues/65 (for context)"},"comment":{"url":"https://api.github.com/repos/dask/distributed/issues/comments/386105252","html_url":"https://github.com/dask/distributed/issues/1951#issuecomment-386105252","issue_url":"https://api.github.com/repos/dask/distributed/issues/1951","id":386105252,"user":{"login":"mrocklin","id":306380,"avatar_url":"https://avatars3.githubusercontent.com/u/306380?v=4","gravatar_id":"","url":"https://api.github.com/users/mrocklin","html_url":"https://github.com/mrocklin","followers_url":"https://api.github.com/users/mrocklin/followers","following_url":"https://api.github.com/users/mrocklin/following{/other_user}","gists_url":"https://api.github.com/users/mrocklin/gists{/gist_id}","starred_url":"https://api.github.com/users/mrocklin/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mrocklin/subscriptions","organizations_url":"https://api.github.com/users/mrocklin/orgs","repos_url":"https://api.github.com/users/mrocklin/repos","events_url":"https://api.github.com/users/mrocklin/events{/privacy}","received_events_url":"https://api.github.com/users/mrocklin/received_events","type":"User","site_admin":false},"created_at":"2018-05-02T20:10:53Z","updated_at":"2018-05-02T20:10:53Z","author_association":"OWNER","body":"Scale down is used here as a method of last resort to kill jobs after they\nshould already have been closed down smoothly.  We don't have to do this\nthough.  Retiring along is probably sufficient.\n\nOn Wed, May 2, 2018 at 3:09 PM, jakirkham <notifications@github.com> wrote:\n\n> It appears that Distributed's Adaptive tells the Scheduler to\n> retire_workers and then scale_down the Cluster\n> <https://github.com/dask/distributed/blob/1.21.7/distributed/deploy/adaptive.py#L230-L235>.\n> Is there a reason both of these operations are needed? Also what does this\n> mean for downstream libraries inheriting from Distributed's Adaptive or\n> Distributed's Cluster?\n>\n> —\n> You are receiving this because you are subscribed to this thread.\n> Reply to this email directly, view it on GitHub\n> <https://github.com/dask/distributed/issues/1951>, or mute the thread\n> <https://github.com/notifications/unsubscribe-auth/AASszJ3XDA_0H8yyTer51ESoe3oXdmxMks5tugRkgaJpZM4TwAF_>\n> .\n>\n"}}
{"actor":{"display_login":"mrocklin"}}