-
Notifications
You must be signed in to change notification settings - Fork 37
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
Support inbound Connector restarts #3319
Labels
kind:enhancement
New feature or request
Comments
sbuettner
changed the title
Support re-activations for inbound Connectors
Support inbound Connector restarts
Sep 24, 2024
1 task
This was
linked to
pull requests
Oct 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Is your feature request related to a problem? Please describe.
There is currently no simple restart mechanism for Inbound Connectors that can be used by developers to restart their Connectors. In case of any client exceptions like networking issues the inbound Connectors are stopping and users have to manually re-deploy their processes to re-activate them.
This is not a great user experience and we can improve this situation with a solution that we already have tested in the Kafka Connector: https://github.com/camunda/connectors/blob/main/connectors/kafka/src/main/java/io/camunda/connector/kafka/inbound/KafkaConnectorConsumer.java#L116
Describe the solution you'd like
We want to simplify the developer experience of handling restarts for inbound connectors and would therefore enhance the existing
cancel(final Throwable exception)
method implementation.The
cancel
method should check the exception and should look for a specific type like for exampleRestartException
. If this exception is thrown the runtime should restart the Connector using the exception properties like backoff time or restart delay.The text was updated successfully, but these errors were encountered: