mongo-cluster-docker

Forked from: https://github.com/senssei/mongo-cluster-docker

The project is adapted to run 8 primary instances on a single Rancher host (32 GB RAM), and 8 secondary instance + 8 arbiters on another host (8GB RAM).

Access control is enabled. Configure .env file.

Run locally:

./s/compose-up.sh

Configure load_env_file.sh and run in Rancher:

./s/prod-compose-up.sh

Originally:

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:

1. https://warzycha.pl/mongo-db-sharding-docker-example/
2. https://warzycha.pl/mongo-db-shards-by-location/

Run

docker-compose -f docker-compose.1.yml -f docker-compose.2.yml  -f docker-compose.cnf.yml -f docker-compose.shard.yml up

or

./compose.sh up

Tests

Manually for the time being

0. Core tests

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:

Sharding configuration

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.

Issues and limitations

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. :)

Reference

• http://www.sohamkamani.com/blog/2016/06/30/docker-mongo-replica-set/
• https://github.com/singram/mongo-docker-compose
• http://stackoverflow.com/questions/31138631/configuring-mongodb-replica-set-from-docker-compose
• https://gist.github.com/garycrawford/0a45f820e146917d231d
• http://stackoverflow.com/questions/31746182/docker-compose-wait-for-container-x-before-starting-y
• https://docs.docker.com/compose/startup-order/
• http://stackoverflow.com/questions/31138631/configuring-mongodb-replica-set-from-docker-compose
• https://github.com/soldotno/elastic-mongo/blob/master/docker-compose.yml

Access control:

• https://docs.mongodb.com/v3.4/tutorial/deploy-sharded-cluster-with-keyfile-access-control/

See more @ ENV.md

MIT @ LICENSE