Skip to content

Audit operator code for "overload protection" #302

Description

@frankmcsherry

At least one operator (#301) has an implementation that risks operators getting wedged if they process inputs more slowly than they are produced upstream. Ideally, operators would ensure they perform a finite amount of work each time they are scheduled, but I suspect that many risk continuing to run as long as input data are available.

Activity

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