Moooree!! Please! More! It's insane how well you explain things and how well you give visual feedback when you refer different parts of the code. Thanks for the hardwork on these clips, please stop doing whatever you are doing and record a few more :)
Thank you very much for you comments! jajaja! that would be awesome if I could :D, yeah, I am looking for ways to create better videos and trying to make them as understandable as possible.
@@ManuelGutierrez Hi again. Have you tried the secure version of the mongo replica set in a docker container? I mean the replica set is protected with a username and password.
Greatest video I have seen on this subject. But please can my replicas be on different servers, like 1 mon my local, another replica on mlab and the other on Mongo Atlass? Thanks.
Great tutorial!! Thank you for the knowledge!! I have a question about that. When i make a new docker-compose and i run the containers other time, I have an error. You can see the next in the terminal: setup-rs_1 | MongoDB shell version v4.0.10 setup-rs_1 | connecting to: mongodb://mongo-rs0-1:27017/?gssapiServiceName=mongodb setup-rs_1 | 2019-07-25T18:10:35.648+0000 E QUERY [js] Error: couldn't connect to server mongo-rs0-1:27017, connection attempt failed: SocketException: Error connecting to mongo-rs0-1:27017 (172.27.0.5:27017) :: caused by :: Connection refused : mongodb-replicaset_setup-rs_1 exited with code 1. After that i could see that my database doesn't exist. Could you help me please? Thank you for all and we are waiting for more tutorials like this.
Hi Jon L, :( you are right I tested this a couple of months ago and it was working but now it is displaying that message, I am trying to fix it on my spare time, will let you know once I find the issue and fix it!, thanks for letting me know and I do apologize about the issue
Hi, I have a noob question. For development, having all replica sets in the same machine works. But, for production deployment this will not have much value, right? Because, the point of having replica sets is if primary node goes down then a new primary will be chosen among other replica sets thus ensuring we can always read and write even when one database has gone down. So, deploying all replica sets to the single server or a single digitalocean droplet dont make sense because when they fail, they all fail together. Am I right?
Bonjour Arnob Chowdhury, yes you are right, if you have multiple nodes in just one server, you will only get a protection if one of those nodes goes down, but it will not protect you when the server fails, for production it makes more sense to use different isolated servers for each node as you are mentioning :D.
I tried it but facing few issues. Pls help 1. When running docker compose up- the replica set is not configured but all the containers were running using docker desktop - linux containers. 2. Localhost : 1234 for admin is not exposed 3. I tried the command mongo mongodb://Node1:27017 replicascript.js Both in setup Containers and docker compose Adminmongo is not exposed outside. How to test the replica set from outside container - normal app pls help
Hey Rathinam Murugesan, I made some changes that fix some of the issues you described (I tested on a windows machine), you can find them here: github.com/drginm/docker-boilerplates/commit/52cd8aa3855ebe41380927a63f428a861557bf6e. Hope this helps
hello I have windows 10 i clone your github repository , and i execute docker-compose up but i got the error: mongodb-replicaset-mongo-rs0-1-1 | {"t":{"$date":"2022-08-31T13:25:34.876+00:00"},"s":"I", "c":"-", "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":{"error":"NotYetInitialized: Cannot use non-local read concern until replica set is finished initializing.","nextWakeupMillis":17800}}
Hey can you explain how you fixed the issue. i''m still getting "Error: couldn't connect to server mongo-rs0-1:27017, connection attempt failed: SocketException: Error connecting to mongo-rs0-1:27017 : caused by :: Connection refused"
![[ MongoDB 7 ] Set up Sharding in MongoDB using Docker containers](http://i.ytimg.com/vi/7Lp6R4CmuKE/mqdefault.jpg)
Moooree!! Please! More!
It's insane how well you explain things and how well you give visual feedback when you refer different parts of the code.
Thanks for the hardwork on these clips, please stop doing whatever you are doing and record a few more :)
Thank you very much for you comments! jajaja! that would be awesome if I could :D, yeah, I am looking for ways to create better videos and trying to make them as understandable as possible.
thats what i need, i like that
I wish I had seen this before... Great video!! Thank you!
I am glad you liked it! thanks!!!
Great video, excellent explanation!!
Thank you very much Luuk th! :D
fantastic video!!!!! any GitHub repo for the material? thank you! works great in Mac, got it working in Windows 10 by creating Volumes name.
A tip : watch series at flixzone. Been using it for watching lots of of movies lately.
@Moses Watson yup, have been watching on Flixzone for years myself :)
@Moses Watson definitely, have been watching on Flixzone for since december myself :D
@Moses Watson yup, I've been using flixzone for since december myself :D
Thanks for the great tutor.
Thank you!!! :D
@@ManuelGutierrez Hi again. Have you tried the secure version of the mongo replica set in a docker container? I mean the replica set is protected with a username and password.
@Tuncay Sonmez, hummm, nope not yet, will certainly add it into my backlog to create one in the future!, thanks!
Greatest video I have seen on this subject. But please can my replicas be on different servers, like 1 mon my local, another replica on mlab and the other on Mongo Atlass?
Thanks.
I am getting "Error parsing YAML config file: yaml-cpp: error at line 2, column 13: illegal map value" though I am using exact code
Great tutorial!! Thank you for the knowledge!!
I have a question about that. When i make a new docker-compose and i run the containers other time, I have an error. You can see the next in the terminal:
setup-rs_1 | MongoDB shell version v4.0.10
setup-rs_1 | connecting to: mongodb://mongo-rs0-1:27017/?gssapiServiceName=mongodb
setup-rs_1 | 2019-07-25T18:10:35.648+0000 E QUERY [js] Error: couldn't connect to server mongo-rs0-1:27017, connection attempt failed: SocketException: Error connecting to mongo-rs0-1:27017 (172.27.0.5:27017) :: caused by :: Connection refused :
mongodb-replicaset_setup-rs_1 exited with code 1.
After that i could see that my database doesn't exist. Could you help me please?
Thank you for all and we are waiting for more tutorials like this.
Hi Jon L, :( you are right I tested this a couple of months ago and it was working but now it is displaying that message, I am trying to fix it on my spare time, will let you know once I find the issue and fix it!, thanks for letting me know and I do apologize about the issue
Hi, I have a noob question. For development, having all replica sets in the same machine works. But, for production deployment this will not have much value, right? Because, the point of having replica sets is if primary node goes down then a new primary will be chosen among other replica sets thus ensuring we can always read and write even when one database has gone down. So, deploying all replica sets to the single server or a single digitalocean droplet dont make sense because when they fail, they all fail together.
Am I right?
Bonjour Arnob Chowdhury, yes you are right, if you have multiple nodes in just one server, you will only get a protection if one of those nodes goes down, but it will not protect you when the server fails, for production it makes more sense to use different isolated servers for each node as you are mentioning :D.
@@ManuelGutierrez hi, thanks for the reply. 🙂
I tried it but facing few issues. Pls help
1. When running docker compose up- the replica set is not configured but all the containers were running using docker desktop - linux containers.
2. Localhost : 1234 for admin is not exposed
3. I tried the command mongo mongodb://Node1:27017 replicascript.js
Both in setup Containers and docker compose
Adminmongo is not exposed outside. How to test the replica set from outside container - normal app pls help
Hey Rathinam Murugesan, I made some changes that fix some of the issues you described (I tested on a windows machine), you can find them here: github.com/drginm/docker-boilerplates/commit/52cd8aa3855ebe41380927a63f428a861557bf6e. Hope this helps
Where is the authentication for the replicaset?
hello I have windows 10 i clone your github repository , and i execute docker-compose up but i got the error: mongodb-replicaset-mongo-rs0-1-1 | {"t":{"$date":"2022-08-31T13:25:34.876+00:00"},"s":"I", "c":"-", "id":4939300, "ctx":"monitoring-keys-for-HMAC","msg":"Failed to refresh key cache","attr":{"error":"NotYetInitialized: Cannot use non-local read concern until replica set is finished initializing.","nextWakeupMillis":17800}}
If you get errors about connection refused in setup.sh, I fixed this by putting all the containers on the same "network" in docker-compose file.
Hey can you explain how you fixed the issue. i''m still getting "Error: couldn't connect to server mongo-rs0-1:27017, connection attempt failed: SocketException: Error connecting to mongo-rs0-1:27017 : caused by :: Connection refused"