Skip to content

Commit

Permalink
Merge branch 'release-6.0.0'
Browse files Browse the repository at this point in the history
  • Loading branch information
jasonmp85 committed Nov 10, 2016
2 parents 8685eae + df67715 commit 5f253f6
Show file tree
Hide file tree
Showing 6 changed files with 16 additions and 8 deletions.
6 changes: 6 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
@@ -1,3 +1,9 @@
### citus-docker v6.0.0 (November 9, 2016) ###

* Bump Citus version to 6.0.0

* Based on latest PostgreSQL 9.6.1 image and official Citus 6.0.0 package

### citus-docker v5.2.2 (November 8, 2016) ###

* Bump Citus version to 5.2.2
Expand Down
4 changes: 2 additions & 2 deletions Dockerfile
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
FROM postgres:9.5.5
FROM postgres:9.6.1
MAINTAINER Citus Data https://citusdata.com

ENV CITUS_VERSION 5.2.2.citus-1
ENV CITUS_VERSION 6.0.0.citus-1

# install Citus
RUN apt-get update \
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -84,7 +84,7 @@ SELECT master_get_active_worker_nodes();
-- (5 rows)
```

If you inspect the configuration file, you’ll find that there is a container that is neither a master nor worker node: `citus_config`. It simply listens for new containers tagged with the worker role, then adds them to the config file in a volume shared with the master node. If nodes have been added or removed, it sends a `SIGHUP` signal to the master to reload the config. See Citus’ [`workerlist-gen`][workerlist-gen] repo for more details.
If you inspect the configuration file, you’ll find that there is a container that is neither a master nor worker node: `citus_config`. It simply listens for new containers tagged with the worker role, then adds them to the config file in a volume shared with the master node. If new nodes have appeared, it calls `master_initialize_node_metadata` against the master to repopulate the node table. See Citus’ [`workerlist-gen`][workerlist-gen] repo for more details.

You can stop your cluster with `docker-compose -p citus down`.

Expand Down
7 changes: 4 additions & 3 deletions docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -3,14 +3,15 @@ version: '2'
services:
master:
container_name: 'citus_master'
image: 'citusdata/citus:5.2.2'
image: 'citusdata/citus:6.0.0'
ports: ['5432:5432']
labels: ['com.citusdata.role=Master']
volumes: ['/var/run/postgresql']
worker:
image: 'citusdata/citus:5.2.2'
image: 'citusdata/citus:6.0.0'
labels: ['com.citusdata.role=Worker']
config:
container_name: 'citus_config'
image: 'citusdata/workerlist-gen:0.9.0'
image: 'citusdata/workerlist-gen:2.0.0'
volumes: ['/var/run/docker.sock:/tmp/docker.sock']
volumes_from: ['master']
3 changes: 2 additions & 1 deletion nightly/docker-compose.yml
Original file line number Diff line number Diff line change
Expand Up @@ -6,11 +6,12 @@ services:
image: 'citusdata/citus:nightly'
ports: ['5432:5432']
labels: ['com.citusdata.role=Master']
volumes: ['/var/run/postgresql']
worker:
image: 'citusdata/citus:nightly'
labels: ['com.citusdata.role=Worker']
config:
container_name: 'citus_config'
image: 'citusdata/workerlist-gen:0.9.0'
image: 'citusdata/workerlist-gen:2.0.0'
volumes: ['/var/run/docker.sock:/tmp/docker.sock']
volumes_from: ['master']
2 changes: 1 addition & 1 deletion tutum.yml
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ worker:
target_num_containers: 2
tags: ['worker']
config:
image: 'citusdata/dockercloud-workerlist-gen:0.9.0'
image: 'citusdata/dockercloud-workerlist-gen:1.0.0'
volumes: ['/var/run/docker.sock:/tmp/docker.sock']
volumes_from: ['master']
roles: ['global']
Expand Down

0 comments on commit 5f253f6

Please sign in to comment.