Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.0.0
-
None
Description
If kafka broker path is invalid or inaccurate, ConsumeKafka processor can get stuck (concurrent tasks cannot be stopped in a clustered mode). Please refer to the images in the attachment. It appears that a configurable timeout property would potentially solve the problem.
Attachments
Attachments
Issue Links
- links to