Consolidate KafkaEventSubscriber and KafkaOutboxSubscriber into the former (GSI-1405) #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context:
DLQ retry topic subscription in select services
Problem description:
The services listed below run both event subscribers and outbox subscribers simultaneously.
This has not been a problem until now because the subscribed topics have been mutually exclusive.
The DLQ process introduced retry topics, of which there exists 1 per service.
Both retried outbox events and retried normal events both get funneled into the same retry topic for a service.
Both the outbox consumer and event consumer try to subscribe to the service's retry topic, but only one gets the events (barring a rebalance).
Affected Services:
Notes:
Preliminary Conclusion:
Given the problem stems from the fact that there are potentially two running consumers that listen to the same topic,
there are two obvious approaches to fix the problem: