Command Center allows you to view resource groups that have been created in Greenplum Database, to add or delete resource groups, and to edit the resource group attributes Concurrency, CPU %, and Memory %.
To change values of the
MEMORY_SPILL_RATIO resource group attributes, use the
ALTER RESOURCE GROUP SQL command.
Click EDIT to open the Resource Group editor.
To delete a resource group, select the resource group, and click the minus sign that appears at the right.
You cannot delete the
admin_groupresource groups. You cannot delete a resource group that is assigned to any Greenplum Database role.
To add a resource group, click ADD RESOURCE GROUP and enter a name for the resource group in the Name column. Resource group names must be unique and are case-sensitive.
Adjust the values of the Concurrency, CPU %, and Memory % resource group attributes.
- The maximum number of concurrent transactions, including active and idle transactions, that are permitted in the resource group. Concurrency sets theCPU %
CONCURRENCYattribute of the resource group. The total of the Concurrency columns cannot exceed the value of the Greenplum Database
max_connectionsmaster server configuration parameter.
- The percentage of CPU resources available to this resource group. The percentage is the portion of the total CPU percentage allocated for all resource groups (reserved CPUs excluded), which is set with theMemory %
gp_resource_group_cpu_limitserver configuration parameter. CPU % sets the
CPU_RATE_LIMITattribute of the resource group.
- The percentage of memory resources available to this resource group. The percentage is the portion of the total memory allocated for all resource groups, which is set with theMemory Spill Ratio %
gp_resource_group_memory_limitGreenplum Database configuration parameter. Changing the Memory % value sets the
MEMORY_LIMITattribute of the resource group.
- The memory usage threshold for memory-intensive transactions. When a transaction reaches this threshold, it spills to disk.Statement Memory
- The amount of memory allocated to a query. This column is recalculated as you adjust other resource group settings. If a query needs more memory, it is allocated from the resource group shared memory pool and the global shared memory pool, if available.
The totals of the CPU % and Memory % columns must not exceed 100%. You should not allow the total of the CPU % column to exceed 90%, because this could cause resource-intensive queries to consume nearly all CPU, starving other Greenplum Database processes. If the total of the Memory % column is less than 100%, the unreserved memory is part of the resource group shared global memory pool. See “Global Shared Memory” in Using Resource Groups in the Greenplum Database Administrator Guide for information about the global resource group shared memory pool.
- The maximum number of concurrent transactions, including active and idle transactions, that are permitted in the resource group. Concurrency sets the
Click Apply to save your changes or click Cancel to abandon your changes.
Every Greenplum Database role is assigned to a single resource group in the
pg_roles system table. Transactions executed by a role are managed by its assigned resource group, unless you create an assignment rule to override the default.
You can view the current resource group assignments for all roles and change a role’s resource group by adding it to a different resource group.
To move a role to a different resource group:
Enter all or part of the role name in the add role field beneath the new resource group.
Choose the role from the list that is displayed and press Enter.
The change is immediately applied to the Greenplum Database
pg_roles system table.
Timeout rules set the amount of time a session can be idle before it is terminated. You create a timeout rule for each resource group. See About Timeout Rules for more information about timeout rules.
To add a timeout rule, click EDIT in the Idle Connections Management section.
Click ADD TIMEOUT RULE and fill in the fields.
- Choose a resource group from the list.Time before idle connections killed
- The amount of time before an idle session is terminated. Enter an integer value for the number of seconds or minutes and choose minutes or seconds from the list. A value of 600 seconds, for example, terminates the session after it has been idle for 10 minutes. See About Timeout Rules for warnings about setting timeouts for theExempted roles
admin_groupresource group and resource groups with roles that require persistent sessions.
- The rule is not applied to roles added to this field. Open the list to choose roles to exempt from the rule. Only roles for the selected resource group are included in the list. To remove a role from the field, click the x next to the role name.Message
- Enter the message to log when a session is killed by this rule.
Click APPLY to save your changes.