No additional debugging info should need to be enabled (at least initially). You should start by only starting one drillbit and then providing drillbit.log. When I've seen this before there was an associated warning in drillbit.log when this type of failure occurred. I would like to see if we're seeing the same thing here.
thanks, Jacques On Mon, Jun 1, 2015 at 10:47 AM, Rangaswamy, Manoharan <[email protected] > wrote: > Hi Jacques, > > > > I saw your reply in the mail list and responding to your question. > > > > Can you please let me know if you want me to execute the failing operation > now and send the log files or setup some more debug info options and send > the log file. Please let me know. > > > > Thanks, > > Mano > > *From:* Rangaswamy, Manoharan > *Sent:* Monday, June 01, 2015 8:24 AM > *To:* '[email protected]' > *Subject:* MapR Drill - mongodb collections does not show up > > > > We are using MapR Drill 1.0 and configured a mongodb storage plugin as > below. > > > > { > > "type": "mongo", > > "connection": "mongodb://uid:pwd@host:port/dbname", > > "enabled": true > > } > > > > We are able to connect through CLI and Drill Explorer, but it does display > any databases and query against any collection fail as well. > > > > Robomongo connects well with the same user and it works. > > > > Are we missing any additional configuration? Please let us know. > > > > Thanks, > > Mano > > > > >
