Skip to content

[connector/failoverconnector] better handling for no healthy pipelines #46820

@tommyzli

Description

@tommyzli

Component(s)

connector/failover

Is your feature request related to a problem? Please describe.

If each pipeline in the failover priorities reports an error, the connector will be stuck until the retry interval allows it to re-attempt a prior exporter. I think in this case it should at least attempt one loop at retrying the unhealthy consumers. Otherwise a single failure in your last pipeline could result in the collector rejecting data for a significant amount of time

Describe the solution you'd like

The failover connector should try to recheck for healthy pipelines when the last priority pipeline returns an error

Describe alternatives you've considered

No response

Additional context

No response

Tip

React with 👍 to help prioritize this issue. Please use comments to provide useful context, avoiding +1 or me too, to help us triage it. Learn more here.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions