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
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
|
.. _pg_autoctl_activate:
pg_autoctl activate
===================
pg_autoctl activate - Activate a Citus worker from the Citus coordinator
Synopsis
--------
This command calls the Citus “activation” API so that a node can be used to
host shards for your reference and distributed tables.
::
usage: pg_autoctl activate [ --pgdata ]
--pgdata path to data directory
Description
-----------
When creating a Citus worker, ``pg_autoctl create worker`` automatically
activates the worker node to the coordinator. You only need this command
when something unexpected have happened and you want to manually make sure
the worker node has been activated at the Citus coordinator level.
Starting with Citus 10 it is also possible to activate the coordinator
itself as a node with shard placement. Use ``pg_autoctl activate`` on your
Citus coordinator node manually to use that feature.
When the Citus coordinator is activated, an extra step is then needed for it
to host shards of distributed tables. If you want your coordinator to have
shards, then have a look at the Citus API citus_set_node_property_ to set
the ``shouldhaveshards`` property to ``true``.
.. _citus_set_node_property:
http://docs.citusdata.com/en/v10.0/develop/api_udf.html#citus-set-node-property
Options
-------
--pgdata
Location of the Postgres node being managed locally. Defaults to the
environment variable ``PGDATA``. Use ``--monitor`` to connect to a monitor
from anywhere, rather than the monitor URI used by a local Postgres node
managed with ``pg_autoctl``.
|
