Fix: Set gRPC reconnection backoff to prevent indefinite hangs#1184
Fix: Set gRPC reconnection backoff to prevent indefinite hangs#1184RickyMoon800 wants to merge 1 commit intoqdrant:masterfrom
Conversation
✅ Deploy Preview for poetic-froyo-8baba7 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughThe Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes 🚥 Pre-merge checks | ✅ 2 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (2 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Problem
In certain network environments (e.g., high-concurrency batch updates), the Python client could hang indefinitely if the connection dropped mid-stream due to default gRPC settings.
Solution
This PR updates
parse_channel_optionsto include standard gRPC reconnection backoff parameters (grpc.initial_reconnect_backoff_msandgrpc.max_reconnect_backoff_ms). This ensures the client follows an exponential backoff strategy instead of hanging or retrying immediately in a tight loop.Impact
Bounty Address (USDT-TRC20):
TPCeXK1ziCgwZM8JgypZzdKxBemV7Q2TJn