Create and Deploy Topology

The final step in your configuration process is to create and deploy the topology. This is the step that finally makes the data store operational based on configurations defined in the previous sections. You first create a topology and then deploy the topology.

The topology create command takes the following arguments:

  • topology name - A string to identify the topology.

  • pool name - A string to identify the Storage Node pool. This pool specifies which group of deployed Storage Nodes the topology should use.

  • number of partitions - The total number of partitions is static and cannot be changed. To know more on how to determine this value, see Number of Partitions.

This command generates a blueprint that defines how the data and services should be physically distributed across the available Storage Nodes in the Storage Node pool.

Once you have created the topology, you can deploy it. The plan deploy-topology command requires a topology name. This command activates the previously defined topology blueprint. It is the step that transitions the database from a planned configuration to an operational state by starting all necessary database services on the specified Storage Nodes.

Now, your data store is fully installed and configured:
kv-> topology create -name topo -pool BostonPool -partitions 300
Created: topo
kv-> plan deploy-topology -name topo -wait
Executed plan 6, waiting for completion...
Plan 6 ended successfully

Note:

If you have not created an explicit Storage pool , use -pool AllStorageNodes in the above command.

As a final sanity check, you can confirm that all of the plans succeeded using the show plans command: 

kv-> show plans
Output:
1 Deploy Zone (1) SUCCEEDED
2 Deploy Storage Node (2) SUCCEEDED
3 Deploy Admin Service (3) SUCCEEDED
4 Deploy-RepNodes (4) SUCCEEDED