Connection to MongoDB (AWS DocumentDB) fails - Timeout always

Get Help
1

Hi,

I'm facing timedout issue's to connect to AWS DocumentDB(mongo) and metabase always timedout. I had checked the logs seems connection is proper, sometime metabase is able to get collections on the database and most of the time finding problem with timeout.

Timeout issuing is happending only on the AWS documentDB(mongo) and other database engine works as expected even when caching is disabled on metabase.

Timed out while waiting for a server that matches ReadPreferenceServerSelector{readPreference=ReadPreference{name=primaryPreferred, hedgeOptions=null}}. Client view of cluster state is {type=UNKNOWN, servers=[{address:27017=xyz.elb.eu-south-1.amazonaws.com, type=UNKNOWN, state=CONNECTING}]

Here is the connectivity flow for reference.

+---------------------+
| Metabase |
| (BI Tool) |
+----------+----------+
|
| (HTTPS/TLS)
|
+----------v----------+
| Network Load |
| Balancer (NLB) |
+----------+----------+
|
| (TCP/27017)
|
+----------v------------+
| AWS DocumentDB |
| (MongoDB Compatible)|
+-----------------------+

Can anyone of you faced same/similar issue's with documentDB? Tried to tweak connection strings with increasing timeout, however issue doesn't fix and metabase always try to query the collections and as the result metabase get timedout.
How to resolve the issue permanently?

2

Following up on the issue that I'm facing with AWS documentDB and metabase will be really helpful if someone else would also faced and found any solution to address the issue?

3

Any update on the above issue? I was expecting someone from metabase will response on the issue and wanted to let know this is a burning issue and need to find a solution.

4

Please check my message on the github issue, we won't support DocumentDB in the short/near term