--
You received this message because you are subscribed to the Google Groups "ReactiveMongo - http://reactivemongo.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to reactivemong...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reactivemongo/686f71d9-a0da-4738-8af6-a554adc92e32n%40googlegroups.com.
I am not really sure what you mean.Are you saying that you (or other experiential data / driver deployments) have never seen an issue with Atlas elections?
I have tried 4 (not-related to my codebase) opensource reactivemongo (with play or akka-http) projects and they all react the same way. I’ve tried a couple with Java 11 and Java 17.
Really posting once more in case the particular logging events shed light on anything Atlas or RM could be doing.
i. Then a Got an error, no more attempts to do. Completing with a failure...
ii. Error during processing of request: 'MongoError['No primary node is available! (Supervisor-1/Connection-1)']'. Completing with 500 Internal Server Error response. To change default exception handling behavior, provide a custom ExceptionHandler. (reactivemongo.core.actors.Exceptions$PrimaryUnavailableException: MongoError['No primary node is available! (Supervisor-1/Connection-1)'])
If there is an opensource or shareable source project that has success recovering (quickly) from a mongodb election process, would they be willing to share to test with?
Thanks in advance. I realize that a lot of hours have been put into reactivemongo. I’m just blocked hard on redundancy and recovery.
--
You received this message because you are subscribed to a topic in the Google Groups "ReactiveMongo -
http://reactivemongo.org" group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/reactivemongo/J3ezltdp_eY/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
reactivemong...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/reactivemongo/4d56a9e9-ec2d-4a7b-ad60-87033037d1fen%40googlegroups.com.
FWIW, I have no val or lazy val associations with database or collections in code. Our collection code uses the `trait WithCollection[C <: Collection]`
It’s just strange to me that I have tried other code-bases (assuming we aren’t *all* doing something wrong) that don’t work with Atlas primary election sequences. There are a couple others reporting the same type of behaviour as well.
I am willing to try any suggestions that folks might have. I did notice after re-reading compatibility that I am running java 17 (wasn’t sure if there was a potential issue there), Akka 2.6.19, and Play 2.8.17.
Thanks.
--
You received this message because you are subscribed to the Google Groups "ReactiveMongo -
http://reactivemongo.org" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
reactivemong...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/reactivemongo/553ec194-f0df-418c-9b4f-eccba20433e7n%40googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/reactivemongo/BYAPR18MB30645350B43FE4153E0BE31DCDD39%40BYAPR18MB3064.namprd18.prod.outlook.com.
Preliminary testing for me yielded successful results (using Atlas “test resilience” functionality). Thanks for the notification on this. I realize it’s still RC, but that is a very welcome fix.
Thanks!
To view this discussion on the web visit https://groups.google.com/d/msgid/reactivemongo/00b7dfa7-678a-437c-972b-30bb7f377f81n%40googlegroups.com.