This is a simple 3 node replica mongodb setup based on official mongo
docker image using docker-compose
described in my blogpost at https://warzycha.pl/mongo-db-sharding-docker-example/.
For details description, steps and discussion go to:
docker-compose -f docker-compose.1.yml -f docker-compose.2.yml -f docker-compose.cnf.yml -f docker-compose.shard.yml up
Manually for the time being
Basic replica test on rs1 replica set (data nodes), mongo-1-1
rs.status();
this should return in members
3 nodes.
Basic sharding test on router (mongos), mongo-router
sh.status();
this should return something similar to:
--- Sharding Status ---
sharding version: {
"_id" : 1,
"minCompatibleVersion" : 5,
"currentVersion" : 6,
"clusterId" : ObjectId("587d306454828b89adaca524")
}
shards:
active mongoses:
"3.4.1" : 1
balancer:
Currently enabled: yes
Currently running: yes
Balancer lock taken at Mon Jan 16 2017 22:18:53 GMT+0100 by ConfigServer:Balancer
Failed balancer rounds in last 5 attempts: 0
Migration Results for the last 24 hours:
No recent migrations
databases:
Connect to 'mongos' router and run queries/shard-status.js
for shard status.
To establish location based partitioning on it just run queries/init.js
.
It's sometimes stuck on 'mongo-router | 2017-01-16T21:29:48.573+0000 W NETWORK [replSetDistLockPinger] No primary detected for
set cnf-serv'. It's because quite random order in docker-compose
.
My workaround was just to kill all containers related.
docker-compose -f docker-compose.1.yml -f docker-compose.2.yml -f docker-compose.cnf.yml -f docker-compose.shard.yml rm -f
Please pull request. :)
Basically mongosetup
service is now splitted to multiple yml
files. :)
See more @ ENV.md
MIT @ LICENSE