Skip to end of metadata
Go to start of metadata

ClustrixDB provides support for parallel replication which distributes replication overhead between nodes in the cluster, allowing for more parallelism.

At this time, ClustrixDB only provides Beta support for Parallel Replication.

Configuring Parallel Replication

Configuring binlogs on the master is the same as with non-parallel replication :

CREATE BINLOG binlog name; [LOG()], [FORMAT=ROW|STATEMENT];

Configuring a Parallel Replication Slave:

CREATE SLAVE slave_name PARALLEL_LOG = master_log_name, PARALLEL_POS = position, SLICES = num_slices, BATCH_SIZE_MS = batch_size 
          [, MASTER_HOST = master_host] 
          [, MASTER_USER = master_user] 
          [, MASTER_PASSWORD =  master_password] 
          [, MASTER_PORT = master_port];

The values for PARALLEL_LOG and PARALLEL_POS come from the output of SHOW MASTER STATUS PARALLEL.

To modify slave options:

CHANGE SLAVE slave_name TO master_option;

Viewing Parallel Replication Status:

To display the status of a parallel master: 

SHOW MASTER STATUS PARALLEL;
SHOW ALL MASTER STATUS PARALLEL; 


Displaying the status of a parallel slave is the same as with a serial slave: 

SHOW SLAVE STATUS slave_name;
SHOW SLAVE STATUS; 

How it Works

The ClustrixDB Parallel slave is able to parallelize processing of the replication stream and applies them in batches. Row events from within the same transaction are applied in the same transaction on the slave. Both serial and parallel replication use the same Replication Master for generating binlog(s).

Caveats for Parallel Replication

ClustrixDB Parallel Replication:

  • Can only be used with a ClustrixDB slave. 
  • Is currently offered with beta support only.
  • Can only be used for RBR (row-based replication).
  • Does not support foreign keys.
  • Clustrix parallel replication is only recommended for replicating tables where each unique key has at least one column that is part of the primary key. If any unique key's columns are mutually exclusive from the columns in the primary key, then serial replication is recommended. 
  • No labels