Skip to content

Fail fast on NATS errors #1174

Description

@carlosgjs

Summary

Similar to how Redis failures are handled, if an async job is running and suddenly NATS is unreachable or the task queue for the job doesn't exist the job can be failed so that the user gets feedback. It can then me retried once the system is up again.

See ami/jobs/management/commands/chaos_monkey.py for testing NATS flushing.

Metadata

Metadata

Assignees

No one assigned

    Labels

    PSv2Async & distributed ML backend (PSv2): job state, NATS dispatch, result handling. Umbrella #515.

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions