Skip to content

A exception handling with backoff for when connection to trickle server fails #1

@ad-astra-video

Description

@ad-astra-video

When I restart the Orchestrator the trickle connections spam ConnectionRefusedError tracebacks.

Suggest we add a exception catch and backoff for this. Also just close the subscribers/publishers if off for say 30 seconds?

May be better to close immediately or within 5 seconds though.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or request

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions