Closed amoscatelli closed 1 month ago
/cc @Sgitario (kubernetes), @evanchooly (mongodb), @geoand (kubernetes), @iocanel (kubernetes), @loicmathieu (mongodb)
Any update on this ? I think it would be better to add the websocket area to the issue, is it possible ?
Thank you in advance
Any update on this topic? Having the same error while resolving SRV records.
Which is strange because if I decouple to a simple REST endpoint the same DNS resolution works.
It seems something with websockets dependency is behaving differently
Yes, it's because of the web socket. The work has not started yet.
Any workarounds on this? I have the same issue.
@shrikanthkr just connect to mongo outside of the web socket, that should workaround the issue.
@mkouba is the issue solved with the new WebSockets next?
If so, I would be in favor of closing this one and document it in the MongoDB guide.
@mkouba is the issue solved with the new WebSockets next?
If so, I would be in favor of closing this one and document it in the MongoDB guide.
I have no idea. @amoscatelli would you care to try your reproducer with WS Next instead?
Let's close this for now and we can reopen if necessary
Describe the bug
This is the follow-up of the investigation/discussion here :
31971
The issue is that MongoDB SRV records are not resolved properly ... in some cases.
I have been investigating this issue for weeks now, and finally I discovered it is related to WebSocket only, not Rest endpoints, and this is why other quarkus devs couldn't reproduce it. Also when I run "quarkus dev", locally everything works. The issue is triggered only on my remote Okteto Kubernetes environment.
This is the current state of my investigation :
(*) Failed looking up SRV record / io.smallrye.mutiny.TimeoutException
I managend to identify the real culprit and created a small reproducer.
Also I quote @cescoffier reply :
Expected behavior
MongoDB SRV records should be resolved normally
Actual behavior
MongoDB SRV records are not resolved :
How to Reproduce?
https://github.com/amoscatelli/quarkus-test
These are the env variables I set to build and deploy to Okteto Kubernetes :
Output of
uname -a
orver
No response
Output of
java -version
No response
GraalVM version (if different from Java)
No response
Quarkus version or git rev
3.0.0.Final
Build tool (ie. output of
mvnw --version
orgradlew --version
)No response
Additional information
No response