kafka-retry | Spring Boot microservice providing generic Kafka message retry capability | Microservice library

by IBM Java Version: v0.1.0 License: Apache-2.0

X-Ray Key Features Code Snippets Community Discussions(1)Vulnerabilities Install Support

kandi X-RAY | kafka-retry Summary

kafka-retry is a Java library typically used in Architecture, Microservice, Spring Boot, Kafka applications. kafka-retry has no bugs, it has no vulnerabilities, it has build file available, it has a Permissive License and it has low support. You can download it from GitHub.

In a microservices architecture it is common for applications to communicate via an asynchronous messaging system. A common choice of messaging system is Apache Kafka.

Support

Quality

Security

License

Reuse

Support

kafka-retry has a low active ecosystem.

It has 25 star(s) with 5 fork(s). There are 5 watchers for this library.

It had no major release in the last 6 months.

There are 4 open issues and 0 have been closed. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of kafka-retry is v0.1.0

Quality

kafka-retry has 0 bugs and 0 code smells.

Security

kafka-retry has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

kafka-retry code analysis shows 0 unresolved vulnerabilities.

There are 0 security hotspots that need review.

License

kafka-retry is licensed under the Apache-2.0 License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

kafka-retry releases are not available. You will need to build from source code and install.

Build file is available. You can build the component from source.

Top functions reviewed by kandi - BETA

kandi has reviewed kafka-retry and discovered the below as its top functions. This is intended to give you an instant insight into kafka-retry implemented functionality, and help decide if they suit your requirements.

Returns true if the given request should be retried
Determines if the retry count is exceeded
Determine if the name of the given exception is matching
Get the maximum number of retries
Initialize the stateStores
Initialize state stores
Configures the retry scheduler
Returns true if the given headers are retried
Returns true if the given exception type matches the exception type
Main entry point
Returns the exception message
Send message to origin topic
Dispatches the message based on the configured retry attempts
Send message to permanent failure topic
Drops a message
Adds a message to the retry queue
Process a JSON stream message
Dispatch a message to permanent failure topic
Handles a message
Removes a message from the retry queue
Create the retry headers
Queues a message for retry
Gets queued messages from the message store
Get the minimum dispatch time
Returns the number of retries
Determine if the message should be dropped or not

Get all kandi verified functions for this library.

kafka-retry Key Features

No Key Features are available at this moment for kafka-retry.

kafka-retry Examples and Code Snippets

No Code Snippets are available at this moment for kafka-retry.

Community Discussions

Trending Discussions on kafka-retry

Spring Kafka commit reset offset not work when application goes down

QUESTION

Spring Kafka commit reset offset not work when application goes down

Asked 2020-Apr-15 at 15:41

As described in the documentation, an offset should only be committed when I actually commit (When AckMode.MANUAL_IMMEDIATE or AckMode.MANUAL) or at the end of the listener execution when AckMode.RECORD, however, in the middle of processing the method annotated with @KafkaListener the application goes down, the message is not re-delivered, the application starts reading from the next valid message and this current message is lost (message that was being processed when the application was restarted), how do I achieve the goal of the application reprocessing an uncommitted message when the application is restarted in the middle of processing? I have also tried configuring AUTO_OFFSET_RESET_CONFIG as earliest, latest and none without success in the 3 models. For testing purposes, I created a topic with just one partition, I forced the listener to use the container factory that I define manually. The springboot-version 2.2.6

...

ANSWER

Answered 2020-Apr-15 at 14:58

The offset will not be committed until the acknowledgment.acknowledge() is called. Set the commitLogLevel container property to DEBUG to see commit activity.

auto.offset.reset only applies if the consumer has never committed an offset (new consumer groups only).

If you can't figure it out from the log; edit the question with the log snippet.

Source https://stackoverflow.com/questions/61230915

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install kafka-retry

You can download it from GitHub.
You can use kafka-retry like any standard Java library. Please include the the jar files in your classpath. You can also use any IDE and you can run and debug the kafka-retry component as you would do with any other Java program. Best practice is to use a build tool that supports dependency management such as Maven or Gradle. For Maven installation, please refer maven.apache.org. For Gradle installation, please refer gradle.org .

Support

For any new features, suggestions and bugs create an issue on GitHub. If you have any questions check and ask questions on community page Stack Overflow .

Find more information at: