Documentation — Administrator's guide

Create a production cluster

The installation is the one of a trial cluster, with a configuration file that describes your real machines.

The configuration file

Each line describes one broker. Blank lines are ignored; a comment starts with # in the first column.

SQL_BROKER      NAME  PORT  LINUX_USER  BACKUP_DIRECTORY
MASTER_BROKER   NAME  PORT  DB_USER  DB_PASSWORD  DATABASE
DATA_BROKER     NAME  IP_ADDRESS  PORT  DB_USER  DB_PASSWORD  DATABASE  DATACENTER  RACK  AFFINITY
  • Names are unique in the whole file. Ports are between 1024 and 65535, and the ports of two SQL or master brokers on one machine must not overlap.
  • The backup directory of a SQL broker must be writable: it receives the files of dump table.
  • Give each data broker its datacenter and its rack. Put the data brokers that share a power supply or a switch in the same rack: copies of a table are spread over racks.
  • Use the * affinity unless your support says otherwise.

What install.sh does

  1. Creates bin and etc on this machine and copies the programs and license.txt.
  2. Generates the identifier of the cluster (CLUSTER_UUID) and a secret key (CLUSTER_KEY, 64 hexadecimal characters). The brokers use the key to sign their messages to each other: it is the same on every SQL broker, and the file that contains it is private (etc/synsql.conf, mode 0600).
  3. Writes etc/synsql.conf, and the password files of the master brokers (etc/NAME.magic).
  4. Creates the dictionary on every master broker and registers the data brokers.
  5. Copies the programs, the license, synsql.conf and the password files to the other SQL brokers with scp. The installing machine needs SSH access to them.

After the installation

  • Start synsqld on each SQL broker.
  • Check the license and the cluster: show license; and show cluster;.
  • Change the password of the system account.
  • Create the accounts of your users (create user) and give them privileges (grant).
  • Keep a copy of etc/synsql.conf and of the .magic files in a safe place: they are needed to join a broker to the cluster.

← Create a trial cluster  |  Install clients →