[DOCS-13647] Add deadletterqueue to the Kafka Sink documentation Created: 14/May/20 Updated: 29/Oct/23 Resolved: 03/Jun/20 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | Kafka |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | Robert Walters | Assignee: | Christopher Cho |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | kafka-connect, kafka-documentation | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 3 years, 36 weeks ago |
| Story Points: | 2 |
| Description |
DescriptionWhile not specific to the MongoDB Kafka Connector, the default behavior without defining a dead letter queue will be for the connector to stop and need to be restarted upon the first mal-formed message in the topic. Thus, we should add documentation to the Kafka connector to use a dead letter queue and specify an error tolerance. Here is a link to a blog on dead letter queues for reference https://www.confluent.io/blog/kafka-connect-deep-dive-error-handling-dead-letter-queues/
Scope of changesImpact to Other DocsMVP (Work and Date)Resources (Scope or Design Docs, Invision, etc.) |
| Comments |
| Comment by Githook User [ 03/Jun/20 ] |
|
Author: {'name': 'Chris Cho', 'email': 'chris.cho@10gen.com', 'username': 'ccho-mongodb'}Message: |
| Comment by Githook User [ 03/Jun/20 ] |
|
Author: {'name': 'Chris Cho', 'email': 'chris.cho@10gen.com', 'username': 'ccho-mongodb'}Message: |
| Comment by Githook User [ 03/Jun/20 ] |
|
Author: {'name': 'Chris Cho', 'email': 'chris.cho@10gen.com', 'username': 'ccho-mongodb'}Message: |
| Comment by Christopher Cho [ 02/Jun/20 ] |
|
Ready for review: |