initialPollWaitingForConsumerGroupJoin time should be configurable
See original GitHub issueFrom Slack conversation(Click here to see full details): https://zerocode-workspace.slack.com/archives/C013T2SV151/p1606153188005800
...Probably because the issue am running into is during initialPollWaitingForConsumerGroupJoin(consumer) and there the
consumer poll is hardcoded to 500ms and ofcourse it has retries about 10 times but that does not seem sufficient - may
be for several reasons that broker or kafka server is slow or due to the latency of network etc - but no matter what - i
think the consumer client should be configurable to deal with the intialPoll so its resilient enough to poll and wait for the
kafka response to let the consumer group to join in without timing out
Linked issue: #421 , Linked PR: https://github.com/authorjapps/zerocode/pull/422
Issue Analytics
- State:
- Created 3 years ago
- Comments:8 (7 by maintainers)
Top Results From Across the Web
No results found
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
delivered changes using PR: https://github.com/authorjapps/zerocode/pull/463
hey @dandalavinod . You cant directly push to original zerocode repo. If everyone could directly push the code, it would be huge mess 🤕 ( to say the least). So what you should do is to fork zerocode original repo ( how to do forking is described here ) , you clone forked repo locally, make changes , push changes to your forked repo and propose pull request from forking repo ( you would see it on forked repo page). Hope this helps