Manage brokers

Every command on this page needs an administrator account, and refuses to run when the cluster is locked, unless said otherwise.

Data brokers

create databroker NAME IP PORT USER PASSWORD DATABASE DATACENTER RACK;
alter databroker NAME set offline;
alter databroker NAME set online [force];
drop databroker NAME;

• create databroker connects the new broker first: if the connection fails, nothing is recorded. The new data broker can be used for deployments at once. It is refused when you reached the limit of your license (show cluster; shows it).
• set offline is immediate. New requests no longer use the broker; the ones that already started finish with it.
• set online first connects the broker, then looks for orphan tables on it (tables that the dictionary does not know). Without orphans the broker comes back. With orphans, it stays offline unless you give force, which drops them.
• drop databroker needs the cluster to be locked (lock cluster;) and the data broker to hold no segment.

Master brokers

lock cluster;
create masterbroker NAME IP PORT USER PASSWORD DATABASE [using DIRECTORY];
unlock cluster;
drop masterbroker NAME;

• Lock the cluster first, so that the copy of the dictionary to the new broker is consistent.
• All SQL brokers must be running: the command rewrites synsql.conf and sends it to all of them.
• The dictionary is exported to a temporary file, in /tmp unless you give a directory with using.
• Do not use more than ten master brokers. You cannot drop the last one.

SQL brokers

create synsqlbroker NAME PORT BACKUP_DIRECTORY;
drop synsqlbroker NAME;

create synsqlbroker records the broker in the cluster. You still install the programs, the configuration file and the license on the machine, and start synsqld there (see Start and stop services).

Log level

alter server set log level N;

Changes the amount of messages that the broker you are connected to writes to its log.

Look at the brokers

show servers;, show masterbrokers;, show databrokers;, show connections;.