-
Notifications
You must be signed in to change notification settings - Fork 252
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Unknown error while making a remote service call: Cannot assign requested address #849
Labels
Comments
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight. |
@Doris-Ge Hello, Is there any update? |
@jonathanedey any update on this so far? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
problem
SendEachForMulticast throws exception and cannot proceed the notification messages.
"Unknown error while making a remote service call: Cannot assign requested address"
Our kubernetes pod handles 6 kafka partition, each partition keeps messages that consist of 500 registration ids. Begore the multicast deprecation, older method works but very slow. We changed the method and started to getting many 'Cannot assign requested address' error.
I do not understand if the library that uses http/2 or not.
does the http client of google library benefits from useinf same connection and does is use reactive event pool like webclient of spring boot?
environment
The text was updated successfully, but these errors were encountered: