Rule engine: Kafka consumer group per partition #10728
Merged
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.
Rule engine: Kafka consumer group per partition
Many rule engine's “.topic.” served under a single consumer group:
re-LowPriority-consumer
tb_rule_engine.LowPriority.1
tb_rule_engine.LowPriority.2
tb_rule_engine.LowPriority.3
The problem: one fail - all rebalancing
The solution: use consumer group per topic.partition
Hint: Regarding Kafka partition, we always use a single partition 0. ThingsBoard partition are simple the part a topic name like “*.topic.number”
Tests passed:
General checklist
Front-End feature checklist
Back-End feature checklist