Blizzard/node-rdkafka

Question about commit and disconnect after connection is lost

Open

#27 创建于 2016年8月30日

在 GitHub 查看
 (6 评论) (0 反应) (1 负责人)JavaScript (1,979 star) (385 fork)batch import
help wantedquestion

描述

I noticed that when commit is called while connection to kafka is lost, the function never returns or throws any error.

How should I recover from this state?

I could set a timeout and assume the connection is lost if the function does not return within that period and try to establish connection with a different kafka server. However, the disconnect function does not return either when connection is lost. How do I perform the necessary clean up without the disconnect function?

Thanks in advance

贡献者指南

技术栈
javascriptnodejskafka
领域
backendapidata
议题类型
bug
难度面向新贡献者的预计实现难度，1 表示很小改动，5 表示专家级工作。
3
预计时间有经验贡献者完成调查、实现、测试并准备 pull request 的粗略时间范围。
1-2 days
活动状态议题当前的可参与程度：新鲜、活跃、陈旧、阻塞或等待维护者输入。
stale
清晰度议题是否清楚说明期望改动、验收标准和下一步。
clear
前置要求
Node.jsAsync programmingKafka basics
新手友好度1-100 的估计分数，表示该议题对首次贡献者的友好程度。
40
研究方向
Investigate how node rdkafka handles connection loss in the commit() call. Look at the source code for commit handling and the underlying librdkafka behavior. Possibly add timeout or error handling. Check comments in the issue for any suggestions from maintainers.