[
https://issues.apache.org/jira/browse/DRILL-5206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15832335#comment-15832335
]
Adrian Sanchez del Campo commented on DRILL-5206:
-
Hi @tgrall
I clone your PR built it and I'm having the same issue.
Here's what happening:
I connect to the public exposed mongos (127.0.0.38) using `direct-connection
set to true`. However, it keeps on connecting to 127.0.0.40 which is not open.
Healthy mongodb member 127.0.0.40 mongodb425 -
Healthy mongodb configsvr 127.0.0.35 mongodb1242 -
Healthy mongodb configsvr 127.0.0.34 mongodb1253 -
Healthy mongodb mongos 127.0.0.38 mongodb1476 public*
Healthy mongodb configsvr 127.0.0.36 mongodb1560 -
Healthy mongodb arbiter 127.0.0.41 mongodb1655 -
Healthy mongodb mongos 127.0.0.37 mongodb1980 public*
Healthy mongodb member 127.0.0.39 mongodb2145 -
Healthy mongodb backup 127.0.0.42 mongodb2146 -
> MongoDb connection & non replica sets deployment
>
>
> Key: DRILL-5206
> URL: https://issues.apache.org/jira/browse/DRILL-5206
> Project: Apache Drill
> Issue Type: Bug
>Reporter: Adrian Sanchez del Campo
>
> Hello,
> It looks like Drill is hardwire to only work with replica sets?
> ```
> https://github.com/apache/drill/blob/5a4ad2a88331dfe7561ee76fc87e882afe170681/contrib/storage-mongo/src/main/java/org/apache/drill/exec/store/mongo/MongoGroupScan.java
> ```
> The reason I raise this issue is because while doing some testing I created a
> MongoDB deployment at compose.io. Drill is able to connect to it and list
> databases and collections/tables. However, when trying to query a particular
> collection it times out because it tries to connect to a non-public database
> member.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
