Daily Archives: 29.11.2017
docker-compose for starting aerospike and memcache
Place this config wherever you like (in your project) — for instance, ~/myproj/docker/docker-compose.yml:
|
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 |
version: "2" services: #aerspike as: image: aerospike/aerospike-server volumes: - ./aerospike/etc:/opt/aerospike/etc ports: - 3000:3000 command: [asd, --config-file, /opt/aerospike/etc/docker.conf] memcached: image: memcached ports: - 11211:11211 volumes: #volume for etcd dicovery-data: driver: local #volume for database db-data: driver: local |
And this config for aerospike should be placed in a directory ~/myproj/docker/aerospike/etc/docker.conf After that you should run it like that:
|
1 2 |
cd ~/myproj/docker docker-compose up -d |
When you finished, just run:
|
1 2 |
cd ~/myproj/docker docker-compose down |
https://docs.docker.com/compose/reference/up/
Container insights for golang engineer (k8s docker CPU throttling)
We’ve run into problems on my work when k8s limits cpu to few processors (throttling), while go application can see all of them (setting GO_MAX_PROCS to maximum CPUs available) and go’s scheduler is going crazy because of that during highload (like stress-tests). It is caused by scheduling for, let’s say, 40 processors while you have …