EventGate app configs currently use a single kafka.conf for both producer types. Since the hasty producer does not wait on a delivery report before finishing the HTTP response, it can use a much higher value of queue.buffering.max.ms. However a longer queue.buffering.max.ms will cause a the guaranteed producer to likely block for about that amount of time. We should set the hasty producer with a high value, and the guaranteed producer with a lower value.
Description
Description
Details
Details
Status | Subtype | Assigned | Task | ||
---|---|---|---|---|---|
Resolved | Ottomata | T185233 Modern Event Platform | |||
Resolved | Ottomata | T201068 Modern Event Platform: Stream Intake Service | |||
Resolved | Ottomata | T206785 Modern Event Platform: Stream Intake Service (EventGate): Implementation | |||
Resolved | Ottomata | T219032 EventGate should be able to configure hasty and guaranteed kafka producers individually |
Event Timeline
Comment Actions
Change 499204 had a related patch set uploaded (by Ottomata; owner: Ottomata):
[operations/deployment-charts@master] eventgate-analytics - use different batch settings for kafka producers
Comment Actions
Change 499204 merged by Ottomata:
[operations/deployment-charts@master] eventgate-analytics - use different batch settings for kafka producers