Administration Guide › Set Up Replication › Multiwrite Replication › Configure Multiwrite Replication › Prevent Multiwrite Queues Being Lost When the DSA Stops
Prevent Multiwrite Queues Being Lost When the DSA Stops
If you stop a DSA that has multiwrite queues, those queues are lost. This means that you could lose data. CA Directory helps prevent this loss by letting you specify that a DSA will not stop until its multiwrite queues are empty.
If this configuration item is set to True and you stop the DSA, the DSA stops processing but it does not exit while it has multiwrite queues that contain data.
To prevent multiwrite queues being lost when the DSA stops, using commands
Add the following command to the DSA configuration:
set wait-for-multiwrite = true;
To check if this command is set, use the get dsp command.
To prevent multiwrite queues being lost when the DSA stops, using DXmanager
- Log in to DXmanager as a user with the Change or Superuser role.
- Click the Maps tab, and choose the place where you want to set Wait for Multiwrite to True:
- To set this value for a particular DSA or for the entire backbone, display the Topology map.
- To set this value for all DSAs that serve a namespace partition, display the Namespace map.
- Right-click on the item for which you want to set Wait for Multiwrite to True, and click Edit Properties.
- Find the Replication area, and set Wait for Multiwrite to True.
- Click OK or Finish.
- Save and deploy.
More information:
set wait-for-multiwrite Command
How to Stop a DSA
Force a DSA to Stop Using a Command Line
Force a DSA to Stop Using the DSA Console
