Configuring the ClusterManager

Step 1) Create a new ClusterManager config element.

Note

Please consult VRJConfig manual for directions on adding a new config element.

Tip

If you start typing the name of the config element that you want, VRJConfig will try to find a element that starts with what are typing.

Figure 2.4. Create ClusterManager Element

Create ClusterManager Element

Step 2) Give the new ClusterManager element a unique name.

Note

Cluster Juggler often references config elements by their name directly. This means that we must always have unique names for our config elements.

Figure 2.5. Set Name

Set Name

Step 3) Enter the name of the first plugin that your application requires.

Figure 2.6. Enter Plugin Name

Enter Plugin Name

Step 4) Add a new value and enter the name of each additional plugin that your application requires.

Figure 2.7. Adding more Plugins

Adding more Plugins

Step 5) Select the first node that will be in your cluster.

Note

Nodes are represented by MachineSpecific config elements. VRJConfig will only let you select cluster nodes that have been created for this configuration. This means that you must first create these MachineSpecific config elements while configuring the ClusterNetwork. You can refer to the section called “Configuring the ClusterNetwork” for help configuring the ClusterNetwork.

Figure 2.8. Selecting First Node

Selecting First Node

Step 6) Add a new value for each additioanl node in your cluster.

Figure 2.9. Adding More Nodes

Adding More Nodes

Step 7) Select the node for each additional value you just created.

Note

Nodes are represented by MachineSpecific config elements. VRJConfig will only let you select cluster nodes that have been created for this configuration. This means that you must first create these MachineSpecific config elements while configuring the ClusterNetwork. You can refer to the section called “Configuring the ClusterNetwork” for help configuring the ClusterNetwork.

Figure 2.10. Select Node

Select Node

Step 8) Select the node that is responsible for starting the cluster at the same time.

Note

Currently the ClusterManager is responsible for syncronizing the start of your application across the cluster. In the short future this will move to a new plugin, StartBarrierPlugin. This is required because we can not allow one node to start processing input data before another because it would effect the state of the application.

Figure 2.11. Select Barrier Master

Select Barrier Master