The SRV examples in the Connection String section of the MongoDB manual meet this requirement. However, the text does not really indicate the requirement of two (or more) points. I looked for a clear explanation of the requirement in the Wikipedia article for SRV and RFC2782 registration but found nothing. I have the impression that the requirement may be derived from certain definitions in the RFC text, but it is still not useful for the average user. Also, users should not be required to read the driver specifications. And I get the error message IllegalArgumentException: failure requirements: Invalid URI I opened DOCS-12574 to request an addition to the MongoDB manual to better explain this requirement. I think I have spoken badly here. The two-point (or more) application does not appear to be a requirement of RFC2782. However, this is a prerequisite for MongoDB to use SRV records (probably for security reasons, as mentioned in my last comment in DOCS-12574). In any case, I hope this is something we can clarify in the text of the manual. The error you see is from mongoc_uri_parse_before_slash() in libmongoc after mongoc_uri_parse_srv() failed. Just looking at your connection string, I can tell you that “mongo” is an invalid hostname to use with the mongodb + srv scheme.
When you define a development endpoint, the VPC, subnet, and security groups are validated to ensure that they meet specific requirements. jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-11246/1/pipeline/ Exception in thread “Thread-113” java.lang.IllegalArgumentException: Request failed: PS scheduler process could not be started with exit code 134 If Zeppelin Notepad does not display correctly in your web browser, check Zeppelin`s requirements for browser support. For example, some versions and settings may be required for the Safari browser. You may need to update your browser or use a different browser. Even though valid_hostname() or mongoc_uri_parse_srv() has been changed to allow for an end period, I think the actual host string in the SRV/TXT record would have no period (correct me if I`m wrong) and therefore becomes invalid because there is a different domain name than the originally resolved host string. AFAIK, this behavior is also present for security reasons, to protect against obvious DNS spoofing (for example, foo.example.com resolution results in an SRV record at mitm-attack.com). I have the impression that the requirement may be derived from certain definitions in the RFC text, but it is still not useful for the average user. To work around this, I now have to pass the URI on every call that is an eye injury, for example people.write.format(“com.mongodb.spark.sql.DefaultSource”).mode(“append”).option(“database”,”spark”).option(“collection”, “contacts”).option(“uri”, “mongodb+[srv://tempuser]:temppassword@msft-azure-tp2me.azure.mongodb.net/test”).save() How do I set the URI globally at the Spark session level? Close, but please follow the JIRA ticket linked above for updates. If this is fixed in libmongoc 1.16, it will be included in the next version 1.7.0 of the PHP driver.
If you specified the optional SSH public key, verify that it is a valid SSH public key. For all connections and development endpoints that you use, make sure that your cluster does not lack elastic network interfaces. jenkins.mxnet-ci.amazon-ml.com/blue/organizations/jenkins/incubator-mxnet/detail/PR-11055/26/pipeline/751 Reference: jira.mongodb.org/browse/SPARK-115 I have very little experience with Alpine (we`ve only had a handful of problems with this distribution over the years) and I`ve never worked with Consul. Is the problem you describe related to this article? If so, I wonder if the suggestion to run a local caching DNS server might help. where the variable mygDB is the string of the URI above. Yes, they do. I am afraid that the exam you are proposing will fail in my case.