Skip to content

dask-streamz based on the actor interface #369

Open

Description

@martindurant

The stateful actors of Dask closely match the design of streamz nodes.

If checkpoint/restart is part of the actor code, then a major deficit of the current actors model (loss of data when a worker goes down) would be circumvented.

Activity

  1. martindurant commented on Oct 28, 2020

    @martindurant
    MemberAuthor

    @CJ-Wright , I bet you find this idea fascinating...

  2. roveo commented on Dec 21, 2020

    @roveo
    Contributor

    Are actors stable enough to use? I've been thinking about making something that would continuously maintain the state for some pre-defined computation as new data comes in. Something like differential dataflow, but in python and less head-expolding.

    Also, what happens to an actor if the client exits/crashes? Is the memory on workers released?

  3. martindurant commented on Dec 21, 2020

    @martindurant
    MemberAuthor

    They are not, but could be

    if the client exits/crashes? Is the memory on workers released?

    If the client stops, then yes, futures would be released, and actors should be cleaned up.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions