Viewing Service (Processing Unit) Configuration Information
To view the service (Processing Unit This is the unit of packaging and deployment in the GigaSpaces Data Grid, and is essentially the main GigaSpaces service. The Processing Unit (PU) itself is typically deployed onto the Service Grid. When a Processing Unit is deployed, a Processing Unit instance is the actual runtime entity.) configuration information:
To drill down and see information about a specific service, click the card in the Services area of the Cluster overview page. You can see the following information:
- Name of the service
- Type of service (stateful, stateless, mirror, web, or gateway)
- Number of hosts
- Actual vs. planned partitions
- CPU performance (with average CPU usage over time, in percent)
- RAM utilization (with current utilization over time, in percent)
- IOPS (reads, writes, takes, and executes)
Below the performance graphs, the service instances are listed in a table that contains the following information per instance.
Parameter | Description |
---|---|
ID | Name of the service instance |
Mode | Mode of the instance (primary or backup) |
PID | Process ID of the service instance |
Host | Name and IP address of the machine or JVM Java Virtual Machine. A virtual machine that enables a computer to run Java programs as well as programs written in other languages that are also compiled to Java bytecode. hosting the service instance |
Partition status | Indicates whether the partition is connected or disconnected |
CPU | Amount of CPU resources being used by the service instance, in percent |
RAM | Amount of JVM heap being used by the service instance, in percent (actual/allocated) |
Redolog | Percentage of backlogged transactions that has been restored |
You can filter the table by alert type and instance mode, and sort by any of the columns. You can also do a free text search for the instance name.
Processing Unit
Command:
Description:
Display detailed information for the given Processing Unit.
Input Example:
<GS_HOME>/bin/gs pu info myPu
<GS_HOME>/bin/gs.sh pu info myPu
Output Example:
Parameters and Options:
Item | Name | Description |
---|---|---|
Parameter | name | Name of the Processing Unit for which you want to view the details. |
Processing Unit instance
Command:
gs.{sh/bat} pu info-instance <instance ID>
Description:
Display detailed information for the given Processing Unit instance.
Input Example:
<GS_HOME>/bin/gs pu info-instance mySpace~1_1
<GS_HOME>/bin/gs.sh pu info-instance mySpace~1_1
Output Example:
Parameters and Options:
Item | Name | Description |
---|---|---|
Parameter | <instance ID> | Instance ID of the Processing Unit for which you want to view details. |
Specific Processing Unit
Path
GET /pus/{id}/instances
Description
The Instance ID, Processing Unit name, Host ID, Container ID, Partition ID, and Backup ID are displayed for the specified Processing Unit.
Example Request
curl -X GET --header 'Accept: application/json' 'http://localhost:8090/v2/pus/myPu/instances'
Example Response
{
"id": "myPu~1",
"processingUnitName": "myPu",
"hostId": "gigaspaces.com",
"containerId": "gigaspaces.com~16674",
"partitionId": 0,
"backupId": 0
}
Options
Option | Description | Required |
---|---|---|
host URL | Provide the Host URL where the REST REpresentational State Transfer. Application Programming Interface An API, or application programming interface, is a set of rules that define how applications or devices can connect to and communicate with each other. A REST API is an API that conforms to the design principles of the REST, or representational state transfer architectural style. Manager is running. | Yes |
name | Provide the name of the Processing Unit for which you want to see the configuration details. | Yes |
Specific Processing Unit instance
Path
GET /pus/{id}/instances/{instanceId}
Description
The Instance ID, deployment name, Host ID, Container ID, Partition ID, and Backup ID are displayed for the specified Processing Unit instance.
Example Request
curl -X GET --header 'Accept: application/json' 'http://localhost:8090/v2/pus/myPu/instances/myPu~1'
Example Response
{
"id": "myPu~1",
"deploymentName": "myPu",
"hostId": "gigaspaces.com",
"containerId": "gigaspaces.com~16674",
"partitionId": 0,
"backupId": 0
}
Options
Option | Description | Required |
---|---|---|
host URL | Provide the Host URL where the REST Manager is running. | Yes |
name | Provide the name of the Processing Unit for which you want to see the configuration details. | Yes |
instanceId | Provide the Instance ID of the Processing Unit instance for which you want to see the configuration details. | Yes |
To see specific details about a Processing Unit, Processing Unit instance, or Space Where GigaSpaces data is stored. It is the logical cache that holds data objects in memory and might also hold them in layered in tiering. Data is hosted from multiple SoRs, consolidated as a unified data model. in the Processing Unit view, highlight the required component and click the Config tab on the right.
Processing Unit
The Config tab displays the general Processing Unit parameters as they were defined in the sla.xml file, and how they were actually deployed in runtime.
Item | Description |
---|---|
Type | Indicates whether the Processing Unit is stateful (contains a Space) or stateless (does not contain a Space). |
Application | Client application that is running, if applicable. |
Number of Instances | How many Processing Unit instances have been defined in the sla.xml. |
Number of Backups |
(For partitioned Processing units) How many backup Processing Unit instances have been defined in the sla.xml. The number of backups per partition is zero or one. |
Instances per VM | Maximum number of Processing Unit instances that may be deployed per VM (if the hosts are virtual). |
Instances per Machine | Maximum number of Processing Unit instances that may be deployed per machine (if the hosts are physical). |
Deployment Status |
Current status of the Processing Unit:
|
Planned Instances |
How many Processing Unit instances should be deployed in total, based on the number of instances and number of backups configured in the sla.xml file. The number of backups per partition is zero or one. |
Running Instances | How many Processing Unit instances have been deployed in runtime. |
Managing GSM Grid Service Manager. This is is a service grid component that manages a set of Grid Service Containers (GSCs). A GSM has an API for deploying/undeploying Processing Units. When a GSM is instructed to deploy a Processing Unit, it finds an appropriate, available GSC and tells that GSC to run an instance of that Processing Unit. It then continuously monitors that Processing Unit instance to verify that it is alive, and that the SLA is not breached. | Name, host name, and IP address of the managing Grid Service Manager that deployed the Processing Unit. |
Processing Unit Instance
The Config tab displays each component that was configured in the pu.xml and its properties. For example, embedded Spaces, event containers (notify and/or polling), remote services, etc.
Space
The Config tab displays general information about the Space configuration, along with network and environment information, and the configured memory management properties.
This information is also available in the Configuration pane of the Spaces view when you highlight a Space.
Item | Description | |
---|---|---|
General | ||
Space Schema | Type of schema (default, mirror, or persistent). | |
Secured | Whether or not this Space is secured. | |
Persistent | Whether or not this Space is persistent. | |
Clustered | Whether or not this Space is part of a cluster. | |
Clustered Schema | (If applicable) The cluster topology (partitioned or replicated). | |
Network & Environment | ||
Home Directory | Path where the deployment files are located. | |
Host Name | Name or IP address of the host machine. | |
RMI Registry Port | Port number for the RMI registry. | |
JMX Service URL | Full URL for hte JMX service. | |
Memory Management | ||
Cache Policy | Defined cache policy (all in cache or LRU Last Recently Used. This is a common caching strategy. It defines the policy to evict elements from the cache to make room for new elements when the cache is full, meaning it discards the least recently used items first.) | |
LRU Eviction Batch Size | (LRU only) How many of the oldest data objects to remove if eviction is based on available memory. | |
Cache Size | Amount of memory allocated to the cache. | |
Memory Management State | Whether the memory manager is enabled or disabled. | |
High Watermark | When the amount of used cache memory reaches this value (in %), the memory manager must take action (throw an exception or evict objects). | |
Low Watermark | When the amount of used cache memory reaches this value (in %), the memory manager begins to monitor how much cache memory is left. | |
Write Operation Rejection | When the amount of used cache memory reaches this value (in %), the memory manager begins to block write operations. | |
Write Operation Inspection | When the amount of used cache memory reaches this value (in %), the memory manager begins to monitor write operations. |
Refer to the Admin API topics in the Developers Guide.