Summary: How to deploy two Grid Service Containers (GSCs) using partitioned descriptor. A third is automatically deployed, forming a replicated topology.
A default replicated space deployment descriptor is provided with the product and is set for a deployment of three nodes. Two of the instances are marked as required, meaning that the Service Grid makes its best effort to keep the two instances running on any available machine, even during a failover scenario. The Service Grid is also configured to run a single space instance per container. In a case of load (high CPU utilization), the Service Grid tries to launch another space instance if a Service Container is available for it.
Deploying Replicated space Using CLI
To deploy a replicated space using the Service Grid CLI:
Use the gs-all utility to start the Grid Service Monitor (GSM) and Grid Service Container (GSC). This utility launches both GSM and GSC under the same virtual machine.
Open the command line shell (gs) and change directory to config/deployment
Use the command deploy replicated_cluster.xml command to deploy the replicated space, utilizing the replicated_cluster.xml deployment descriptor file.
The following output is displayed:
gs> deploy replicated_cluster.xml
total 1
Deploying [Replicated Cluster], total services [2] ...
[Look And Feel - ServiceGrid] Replicated GigaSpace provisioned to 11.0.0.6
- There are [Look And Feel - ServiceGrid] service provisioning requests outstanding
Deployment notification time 5015 millis, Command completed
To deploy the second space instance, run a second GSC instance. The Service Grid automatically detects the availability of the new GSC instance and deploys the second space instance into the new container.
Monitoring the Deployed space
Use the list command to view the space instances, the lookup groups they are assigned to, and their host locations.
gs> list
total services 12
[Look And Feel - ServiceGrid] Grid Service Container gs-grid test@11.0.0.6
[2] ReplicatedGigaSpace gigaspaces-1400-045 <?>
[3] ReplicatedGigaSpace gigaspaces-1400-045 <?>
[4] Lookup gs-grid, gigaspaces-14 11.0.0.6
[5] ReplicatedGigaSpace_co gigaspaces-1400-045 <?>
[6] Lookup gs-grid, gigaspaces-14 11.0.0.6
[7] Grid Service Container gs-grid test@11.0.0.6
[8] Grid Service Manager gs-grid test@11.0.0.6
[9] ReplicatedGigaSpace_co gigaspaces-1400-045 <?>
[10] Grid Service Manager gs-grid test@11.0.0.6
[11] ReplicatedGigaSpace gigaspaces-1400-045 <?>
[12] ReplicatedGigaSpace_co gigaspaces-1400-045 <?>
The list space utility can provide more information about the space instances, such as the number of entries and their basic configuration:
Option
Description
list space
Lists all spaces in the network
list space entry
Lists all spaces with a specific count per class
list space stats
Lists all spaces, the count per class, and runtime statistics
Deploying Replicated Space Using Admin UI
To deploy a replicated space using the Service Grid Admin UI:
Start the Service Grid Admin UI, using the gs-ui utility.
When deploying a replicated space, you must start another container before the deployment, by executing <GigaSpaces Root>\bin\gsc.bat. Otherwise your deployment won't be successful.
Alternatively, you can start two containers using the service launcher (see Running Service Grid).
Start the Deployment Wizard by clicking the Deploy button (see screenshot below), and select A Proactive Space as the deployment type. Click Next.
Unable to render embedded object: File (IMG007.gif) not found.
A – Deployment button.
Selecting Application as the deployment type defines a Generic Application Service (see Compute Grid (deprecated)).
Set the deployment parameters:
In the Deployment Name field, enter a name to identify the deployed service.
In the Space Name field, enter a name to identify the space. This name is also used to define the space cluster name.
In the Initial Instance Count field, type 2.
In the Maximum Instance Count field, type 2.
From the Space Schema drop-down menu, select space.
From the Cluster Schema drop-down menu, select async-replicated to deploy an asynchronous replicated space.
Click here to view more details about the deployment parameters.
Parameter
Description
Deployment Name
The space service name.
space Name
The space name. Also used to define the space cluster name.
Initial Instance Count
The minimum number of instances that need to be running at any given point of time. The actual number of instances depends on the availability of the GSC instances. This number is used to handle failover – if the actual number of instances is less than the minimum number, the Service Grid proactively tries to re-deploy a failed service to another available machine.
Maximum Instance Count
The maximum number of instances that need to be running. Relevant for scaling policy – if a scaling event happens (e.g. CPU utilization exceeds a certain level), a new instance is deployed and relieves some of the load from the existing cluster members. These instances are auto-deployed and un-deployed up to the maximum number of instances specified.
Space Schema
Determines the configuration type for the space. Default selects the default schema that comes with GigaSpaces. It can be overwritten by the gs.space.url.arg.schema property. See Schema Basics for more details.
Cluster Schema
Determines the cluster topology. The options in the drop-down menu are based on the basic topologies supported by GigaSpaces. These value can be overwritten by the gs.space.url.arg.cluster_schema property. See Cluster Schemas for more details.
To create a Deployment Descriptor based on the default settings, click the Advanced button. This opens the Deployment Descriptor Generator (deprecated), allowing you to modify the default settings.
When you are done, press Next.
In this step you determine the location of the code of the GigaSpaces service, by selecting a codebase server. This enables the Service Grid to dynamically deploy GigaSpaces instances on machines that do not have GigaSpaces installed. The server location is provided as a URL.
Select one of the GSM instances from the list.
Unable to render embedded object: File (IMG009.gif) not found.
Click Verify. This verifies that the location provided by the deployment descriptor is available. If not, another GSM instance, which maintains a reference to the service, is suggested.
The verification step is required only if the codebase server provided in the deployment descriptor is unavailable.
If you clicked Verify and the server is not verified successfully, this indicates that your HTTP port is not set correctly in the Service Deployment Descriptor. Open the descriptor file, and edit the tag <Parameter Name="httpPort" Value="9010" />, under <Component Name="com.gigaspaces.start">. Set the Value attribute to the current port set on your codebase server.
Once the verification finishes successfully, the Deploy button becomes enabled.
Click the Deploy button to start the deployment process. Current deployment status is shown; wait for deployment to finish or press Dismiss to abort the process.
Unable to render embedded object: File (IMG055.gif) not found.
Viewing the Deployment
In the deployment view, you can see the deployment status: which containers are running, which space is deployed on each container, and so on.
A – the newly deployed space is added to the Service Deployments tree.
B – the green boxes represent the services for the selected deployment. Double-clicking one of these boxes leads you to a window called Space Administration UI, which provides the options to start the space browser and to terminate the service.
C – these buttons represent the containers that are currently running. When pressed, each button shows details of the spaces running in the specified container.
D – a list showing the details of the spaces running in the specified container.
In the Infrastructure View (the space view) you can drill down to the specific space elements and see their contents; see runtime statistics; and run benchmarks.
Previous release
Add GigaSpaces wiki search to your browser search engines! 