MongoDB bi connector v2.0.1, schemaDirectory option

-
This post is to show that mongosqld schemaDirectory option requires the process to restart in order for the new drdl file to be picked up by the process.


Identify mongosqld version

[root@msdlva-dsnavl04 smartDrdl]# mongosqld --version
mongosqld version v2.0.1
git version: 932107fa830951b6601b28cab2df234806cb3cd2


I have started the mongosqld as such 

[root@msdlva-dsnavl04 smartDrdl]# ps -ef | grep mongosqld
root     18506 14799  0 13:37 pts/1    00:00:01 mongosqld --addr=10.155.208.169:3307 --schemaDirectory=/apps/drdl --mongo-uri mongodb://xxx/?replicaSet=yyy --logPath /apps/biLog/mongoBI.log --sslPEMKeyFile=/apps/certs/mongodb.pem --sslAllowInvalidCertificates --auth --verbose=5


Let's check what files are in the drdl directory:

[root@msdlva-dsnavl04 drdl]# ls -altr
total 36
-rw-r--r--  1 root    root    11793 Jul 19 13:35 equipStatus.drdl
-rw-r--r--  1 root    root    18764 Jul 19 13:36 personnel_status.drdl
drwxr-xr-x 11 default default  4096 Jul 19 13:44 ..
drwxr-xr-x  2 root    root       57 Jul 19 13:44 .


Now I am connecting to mongosqld via mysql workbench


We can see the two databases connected correspond to the two files in the directory



Let's move a drdl into the directory

[root@msdlva-dsnavl04 drdl]# cp ../taskStatus.drdl .
[root@msdlva-dsnavl04 drdl]# ls
equipStatus.drdl  personnel_status.drdl  taskStatus.drdl


mongosqld is still running

[root@msdlva-dsnavl04 drdl]# ps -ef | grep mongosqld
root     18506 14799  0 13:37 pts/1    00:00:01 mongosqld --addr=10.155.208.169:3307 --schemaDirectory=/apps/drdl --mongo-uri mongodb://xxx/?replicaSet=yyy --logPath /apps/biLog/mongoBI.log --sslPEMKeyFile=/apps/certs/mongodb.pem --sslAllowInvalidCertificates --auth --verbose=5

Once we refresh the connection via mysql client, we still see only two databases


Now we refresh the process itself by restarting it.

We now see three databases which is consistent with the files we stored in the directory. 

Comments

Post a Comment

Popular posts from this blog

MongoDB tip: 4 ways to modify replica set configuration

-
This is just a quick guide on how to modify your replica set settings in 4 different ways. This guide is assuming you have a functional replica set ready, it doesn't matter if it's a single node or multi-node replica set. In each of the four method, I am looking to modify the priority of the _id=0 node Method 1: Via Mongo Shell Login to your Mongo shell,  simply type in mongo , assuming default port is being used and authentication is not enabled [in Mongo shell] cfg = rs.conf() cfg.members[0].priority=99 rs.reconfig(cfg) # "ok":1 indicates the new configuration has been set  MongoDB Enterprise minvera:PRIMARY> rs.reconfig(cfg) {         "ok" : 1,         "operationTime" : Timestamp(1528464949, 1),         "$clusterTime" : {                 "clusterTime" : Timestamp(1528464949, 1),                 "signature" : {                         "hash" : BinData(0
Read more

MongoDB Quick Note: BI Connector Issue

-
This is just a quick note of what can stop mongosqld from working properly that I wasn't aware of. Background: My work runs everything mongodb inside of docker containers, so sometimes it's not as straight forward to see immediately of what's preventing your container from working properly What happened: I ran into issue that my container does not stay up after I updated my drdl to reflect new fields introduced to the underlying collection. How to debug: Go to the host server, copy out entrypoint.sh and add sleep 100000000 to before mongosqld is executed. This force the container to stay up for us to look into issue. Cause of the issue: When I updated the drdl, I used tab instead of space, which is causing the mongsqld to error out Fix: Just replace tab with space and everything is back to normal
Read more

MongoDB Tips: Kill long running processes

-
This is just a quick and simple script to find all active opid that has been running over 10 seconds and they are running against the databases and collections you can specify in the "ns" filter. It's best to first run db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["equipment.detachment","personnel.detail","personnel.unavailability","personnel.detachment"]}    } ).inprog.forEach(function (doc) { print(doc.opid); }) and verify your output before you execute the kill command in my experience to make sure you are killing the processes that are meant to be killed. Once verifed, simply run: db.currentOp(    {      "active" : true,      "secs_running" : { "$gt" : 10 },      "ns" : {$in:["<db1>.<col1>","<db2>.<col2>","<dbn>.<coln>
Read more