mongodb compass connect to localhost failed

#Mongodb compass connect to localhost failed update
#Mongodb compass connect to localhost failed driver
#Mongodb compass connect to localhost failed windows

If it's there then you need to use the specific roles which were used to create under 'data'. Happy to provide more details to help structuring my question. Two things to note: 'MONGINITDBDATABASE' will not create DB unless it's there in your data volume binding i.e './data:/data/db'. Knime version is KNIME have you seen sthg similar already? Seems I am trying to read the database “config”, instead of the heroku-(), which clearly does not have any collection. “Error during fetching metadata from the database: : Command failed with error 13 (Unauthorized): 'not authorized on config to execute command, nameOnly: true, $db: “config”, $clusterTime:…” When I try to fetch the metadata, I am getting an error which starts with: Then I am using the node “MongoDB reader” but I can not select collection. That seems to connect and that heroku-() would be the name of the database. I am using the “MongoDB connector” as we can see above, using an hostname provided by my tech team (something starting with heroku-(figure and letters)). That worked quite well, but I am struggling with MongoDB so far. Thus, the client can be left in a bad state until the application server is rebooted, for example.I am somewhat new to KNIME and have been trying to connect different data sources within KNIME.

#Mongodb compass connect to localhost failed driver

This results in a server-side error (not master) which is not handled appropriately by the Java driver (this is still under investigation).

#Mongodb compass connect to localhost failed update

Using the above client connection settings, if there is a failover and a delayed DNS record update for the cluster writer endpoint, the client would still try to issue writes to the old writer (now reader after failover). MongoClient mongoClient = MongoClients.create(settings) applyToClusterSettings(builder -> builder.hosts(

run and share the output of the command db.getUsers () db.getUsers () What I suspect is that the first db.getUsers () will list a user with id:test.mongosuperadmin while the second one will produce an empty list. So even if the client settings are initialized like below, all reads would still go to the primary instead of the secondary.įinal ServerAddress serverAddress0 = new ServerAddress('cluster-endpoint', 27317)) įinal MongoCredential credential = MongoCredential.createCredential('xxx',įinal MongoClientSettings settings = MongoClientSettings.builder() connect to your local host instance (presuming it is the RHEL server) like you did in the screenshot where you run db.auth (). This causes the client to disregard the read preference and only connect to the server configured in hosts(). When the client specifies only one host in the hosts() method, the mode is set to ClusterConnectionMode.SINGLE instead of ClusterConnectionMode.MULTIPLE The MongoClient Cluster Settings can be defined using a few different methods, such as hosts(), requiredReplicaSetName(), and mode(). This issue, first discovered in Java Mongo Driver 3.7.x, occurs when a client establishes a connection to Amazon DocumentDB using MongoClientSettings and, specifically, when chaining the applyToClusterSettings method.

#Mongodb compass connect to localhost failed windows

The Region is in the endpoint.Īuthorizing Inbound Traffic for Your Linux InstancesĪuthorizing Inbound Traffic for Your Windows InstancesĬlient read preferences are not honored and some clients cannot write to Amazon DocumentDB after failover unless they reboot. To verify the Region of your Amazon DocumentDB cluster, run theįollowing command. (us-east-1) from US West (Oregon) Region (us-west-2)-the Instance in a Region other than the cluster's Region-forĮxample, trying to connect to a cluster in US East (N. If you try to connect to an Amazon DocumentDB cluster from an Amazon EC2 For more information, see Connecting to an Amazon DocumentDBĪdditionally, if your development environment is in a differentĪmazon VPC, you can also use VPC Peering and connect to your Amazon DocumentDBĬluster from another Amazon VPC in the same region or a different To connect to an Amazon DocumentDB cluster from outside an Amazon VPC, youĬan use an SSH tunnel. Thus, you can't connectĭirectly to your Amazon DocumentDB cluster from your laptop or localĭevelopment environment outside of your VPC. Amazon DocumentDB is virtual private cloud (VPC)-only and does notĬurrently support public endpoints. Trying to connect to an Amazon DocumentDB cluster directly from a publicĮndpoint, such as your laptop or local development machine, willįail.

You are trying to connect to an Amazon DocumentDBĬluster directly from your laptop or local development

Java Mongo driver read preference issue.

Security group blocks inbound connections.