-
Type: Bug
-
Status: Resolved
-
Priority: Blocker
-
Resolution: Fixed
-
Affects Version/s: 10.3
-
Component/s: Streams
-
Release Notes Summary:Long running process for StreamWorkManager is possible.
-
Backlog priority:1,500
-
Sprint:nxcore 10.10.5, nxcore 11.1.1
-
Story Points:2
When using the StreamWorkManager implementation with Kafka, the Kafka is configured with the default LogConfig:
kafka.max.poll.interval.ms=60000 kafka.request.timeout.ms=65000 kafka.max.poll.records=5
This will not work for a slow worker like OrphanVersionsCleanupListener which requires more than one minute on medium/large repository.
The consequence of this misconfiguration can result in blocking completely the worker pool.
A quick fix is to change the default Kafka config to use a higher poll interval like 60min.
The Stream WorkManager may need a dedicated Log Configuration (and Kafka configuration) this will be handled in a dedicated ticket.
- is related to
-
NXDOC-1994 Add emphasis on Kafka max.poll configuration
- Resolved
-
NXP-26631 Use a dedicated LogConfig for the StreamWorkManager
- Open