A cluster can be dropped by invoking the drop-cluster command. A cluster can be
dropped by invoking the command from any node of any connected cluster. The node-id
of any node in the cluster to be dropped needs to be specified.

blobcity>drop-cluster node1

The above command drops the cluster corresponding to node1. The command maybe run
from any node in any of the cluster.

Dropping creates partitions

Dropping a cluster simply creates a partition. The two independently clusters may
continue to operate. They will have all data and be ready to take operations if you desire to
do so. A d-rep cluster when dropped essentially becomes a primary cluster and may then
take transactional operations including insert, update and delete.

Dropping already parted clusters

If a partition has already occurred, and you have a d-rep or a r-rep cluster that is now
operating on its own you can drop it from the other clusters to make it a primary cluster. A
node-id of any node on the same cluster should be specified for the cluster to be dropped.
The other clusters need not be connected to this parted cluster for the operation to work.
If the other clusters come back live later, they will be unable to connect to the cluster
which is now dropped from the cluster pool.