![]() So there is a chance for race conditions where the client tries to connect but mongocryptd process is not ready. As all Trainers are MongoDB domain working professionals so they are having many live projects, trainers will use these projects during training sessions. The code wait until the process is spawned, not until the process is ready. Trainers are certified professionals with 7+ years of experience in their respective domain as well as they are currently working with Top MNCs. You are using Compass Readonly edition, which does not. While the code comment says that the lib will wait until the mongocryptd process is up, it is not what the code does: You are connected to a secondary member of your cluster, which does not support write operations. He checked our source code for the libmongocrypt package. He figured out that there is some sort of race condition in the client between spawning the mongocryptd process and connecting to the cluster. ![]() If he deactivates automatic field level encryption everything works fine as expected. Sometimes he gets MongoServerSelectionError: connect ECONNREFUSED 127.0.0.1:27020 as an error. It basically works, but in about 30% of the function invocations he recieves random errors: Most of the time it is "Current topology does not support sessions" He is on 4.4 cluster with the current NodeJS driver 3.6. Issue 2590 mongodb-js/compass GitHub mongodb-js / compass Public Notifications Fork 114 Star 675 Code Issues 27 Pull requests 10 Actions Wiki Security Insights New issue Current topology does not support sessions. He connects MongoDB Atlas via AWS Lambda and he uses automatic Field Level Encryption. I’m not 100 sure, but these seem like SSL errors. Once the MongoDB Compass is installed, you can proceed to the next step. First, open your MongoDB Compass application and click the Fill in connection fields individually option. Customer via intercom has reported a bug in the source code for the libmongocrypt package He connects MongoDB Atlas via AWS Lambda and he uses automatic Field Level Encryption.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |