Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Circuit Breakers and per event destinations #937

Open
5 tasks
Licenser opened this issue Apr 16, 2021 · 1 comment
Open
5 tasks

Circuit Breakers and per event destinations #937

Licenser opened this issue Apr 16, 2021 · 1 comment
Labels
bug Something isn't working enhancement New feature or request

Comments

@Licenser
Copy link
Member

Describe the problem you are trying to solve

We have circuit breakers that handle when destinations are down and reconnect when they're back up. This is great! We also have sinks that allow customizing the destination on a per event level. This is great too!

Together those two aren't great. When a sink chan have a different destination on a per-event level we can't know if the destination is up or down before we get the event so they can't send circuit breaker events :(

Describe the solution you'd like

  • Identify affected sinks
    • udp
    • rest
    • ...
  • see if this can be handled configurable (i.e. a flag "single destination + CB" vs. "multi destination - CB")

Notes

@Licenser Licenser added bug Something isn't working enhancement New feature or request labels Apr 16, 2021
@mfelsche
Copy link
Member

This will be fixed when we implement Stream Handling throughout the runtime and scope CB events either to the whole sink or to a single stream only. See also the Connectors and Streams RFC: tremor-rs/tremor-rfcs#32

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants