Might be nothing, but noticed it browsing in Kibana:
{ "name": "Error", "stack": "Error: Cannot write SSE event: the response is already finished.\n at KafkaSSE._error (/srv/service/node_modules/kafka-sse/lib/KafkaSSE.js:835:17)\n at _start.catch (/srv/service/node_modules/kafka-sse/lib/KafkaSSE.js:335:26)\n at tryCatcher (/srv/service/node_modules/bluebird/js/release/util.js:16:23)\n at Promise._settlePromiseFromHandler (/srv/service/node_modules/bluebird/js/release/promise.js:547:31)\n at Promise._settlePromise (/srv/service/node_modules/bluebird/js/release/promise.js:604:18)\n at Promise._settlePromise0 (/srv/service/node_modules/bluebird/js/release/promise.js:649:10)\n at Promise._settlePromises (/srv/service/node_modules/bluebird/js/release/promise.js:725:18)\n at _drainQueueStep (/srv/service/node_modules/bluebird/js/release/async.js:93:12)\n at _drainQueue (/srv/service/node_modules/bluebird/js/release/async.js:86:9)\n at Async._drainQueues (/srv/service/node_modules/bluebird/js/release/async.js:102:5)\n at Immediate.Async.drainQueues [as _onImmediate] (/srv/service/node_modules/bluebird/js/release/async.js:15:14)\n at runCallback (timers.js:705:18)\n at tryOnImmediate (timers.js:676:5)\n at processImmediate (timers.js:658:5)", "message": "Cannot write SSE event: the response is already finished." }
hostname | eventstreams-production-6fd7b8788c-267l4 |
---|---|
k8s.host | kubernetes1007.eqiad.wmnet |
k8s.labels.app | eventstreams |
docker.container_id | cb9bd94e87105e6d0b626d24351a9c6e1dd72e5501fdf9129dfe591b98e1895b |