Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/senssei/mongo-cluster-docker
Docker compose config for mongodb cluster
https://github.com/senssei/mongo-cluster-docker
docker docker-compose location-based mongo mongo-cluster-docker mongodb partitioning replicas router shard sharding
Last synced: 4 days ago
JSON representation
Docker compose config for mongodb cluster
- Host: GitHub
- URL: https://github.com/senssei/mongo-cluster-docker
- Owner: senssei
- License: mit
- Created: 2017-01-02T14:52:47.000Z (about 8 years ago)
- Default Branch: master
- Last Pushed: 2019-03-27T03:40:00.000Z (almost 6 years ago)
- Last Synced: 2025-01-09T20:32:26.513Z (12 days ago)
- Topics: docker, docker-compose, location-based, mongo, mongo-cluster-docker, mongodb, partitioning, replicas, router, shard, sharding
- Language: Shell
- Homepage:
- Size: 28.3 KB
- Stars: 185
- Watchers: 12
- Forks: 99
- Open Issues: 2
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
README
# mongo-cluster-docker
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
```
# Tests
> Manually for the time being
0. Core tests
Basic *replica* test on *rs1* replica set (data nodes), `mongo-1-1`
```js
rs.status();
```
this should return in `members` 3 nodes.
Basic *sharding* test on *router* (mongos), `mongo-router`
```js
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
See more @ `ENV.md`
MIT @ `LICENSE`