drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tugdual Grall (JIRA)" <j...@apache.org>
Subject [jira] [Created] (DRILL-4882) Drill does not work when it has only access to "secondary nodes"
Date Wed, 07 Sep 2016 12:36:20 GMT
Tugdual Grall created DRILL-4882:

             Summary: Drill does not work when it has only access to "secondary nodes"
                 Key: DRILL-4882
                 URL: https://issues.apache.org/jira/browse/DRILL-4882
             Project: Apache Drill
          Issue Type: Bug
          Components: Storage - MongoDB
    Affects Versions: 1.8.0, 1.7.0, 1.6.0
         Environment: Drill Stand Alone
Drill in MapR
            Reporter: Tugdual Grall
            Priority: Minor

In some deployments, especially when doing analytics on MongoDB, the application, Drill in
this case, only have access to secondary nodes. 

This is a common choice to avoid overloading the Mongo cluster.

When we have such configuration Drill fail with various exception related to timeout/primary
read preference.

This is due to the fact that some of the "Schema Oriented" methods of MongoDriver are forcing
the read preference to primary. The methods are used in the following place in Drill:



and also the Run command to get information about the type of topology (sharded or not):


3- could be fixed by simply adding a ReadPreference.primaryPreferred() but not sufficient
since we need to have 1 & 2 fixed

This message was sent by Atlassian JIRA

View raw message