-
Sub-task
-
Resolution: Done
-
Normal
-
None
-
None
-
3
-
False
-
-
False
-
Unset
-
CRCPLAN-232 - AuthZ | PRBAC v2 Service Provider Migration Initiation (Internal)
-
-
-
A&M Tech Debt Q10, Access & Management Sprint 95, Access & Management Sprint 95, Access & Management Sprint 96, Access & Management Sprint 97, Access & Management Sprint 98, Access & Management Sprint 99
Determine the correct product config for the relations sink connector and/or validate that the default config satisfies our needs.
The default config for the sink connector – as seen on local – is:
config.action.reload = restart connector.class = org.project_kessel.kafka.relations.sink.RelationsSinkConnector errors.deadletterqueue.context.headers.enable = false errors.deadletterqueue.topic.name = errors.deadletterqueue.topic.replication.factor = 3 errors.log.enable = false errors.log.include.messages = false errors.retry.delay.max.ms = 60000 errors.retry.timeout = 0 errors.tolerance = none header.converter = null key.converter = null name = org.project_kessel.kafka.relations.sink.RelationsSinkConnector predicates = [] tasks.max = 1 topics = [outbox.event.relations-replication-event] topics.regex = transforms = [] value.converter = null
The reference is here:
In particular, we should ensure that the consistency guarantees are adhered to, which involves the retry logic.
See:
KIP-298: Error Handling in Connect
Error Retry Configuration in Kafka Connect
Definition of done:
- Check the existing config parameters.
- Ensure that the config parameters when matched with the retry logic in the code provide the right consistency semantics.
