Loading

How to Check Calculation for allocatedRequestCapacity and allocatedLimitCapacity in RTF

Fecha de publicación: Aug 1, 2025
Pasos

CONTENTS

You are using RTF. You are checking the stats for your RTF cluster via the RTF API and want to understand how "allocatedRequestCapacity" and "allocatedLimitCapacity" are calculated.

Here is the official documentation for the RTF API endpoint: link


STEPS TO FOLLOW

From calling that API, you will see the following response for all of your clusters' nodes. Here is a sample snippet from a cluster's controller node:
  
GET https://anypoint.mulesoft.com/runtimefabric/api/organizations/12345-e6c4-475c-8711-123456/fabrics

Partial response:
  
{
        "id": "f733e07d-fdbb-4f5e-9d47-123456",
        "name": "rtftest",
        "region": "us-west-1",
        "vendor": "gravitational",
        "organizationId": "12345-e6c4-475c-8711-123456",
        "version": "1.10.26",
        "status": "Degraded",
        "desiredVersion": "1.10.26",
        "createdAt": 1632949546643,
        "nodes": [
            {
                "uid": "12345-2169-11ec-8458-123456",
                "name": "172.31.0.114",
                "kubeletVersion": "v1.13.13-gravitational.0",
                "dockerVersion": "docker://18.6.2",
                "role": "controller",
                "status": {
                    "isHealthy": true,
                    "isReady": true,
                    "isSchedulable": true
                },
                "capacity": {
                    "cpu": 1,
                    "cpuMillis": 1340,
                    "memory": "6546Mi",
                    "memoryMi": 6546,
                    "pods": 94
                },
                "allocatedRequestCapacity": {
                    "cpu": 0,
                    "cpuMillis": 660,
                    "memory": "970Mi",
                    "memoryMi": 970,
                    "pods": 16
                },
                "allocatedLimitCapacity": {
                    "cpu": 3,
                    "cpuMillis": 3250,
                    "memory": "2920Mi",
                    "memoryMi": 2920,
                    "pods": 16
                }
            },

You can validate this output by running the following command inside Gravity or using the kubectl command from your terminal for BYOK RTF: 
kubectl describe nodes 172.31.0.114

Here is the output of that command: 
Non-terminated Pods:         (16 in total)
  Namespace                  Name                                       CPU Requests  CPU Limits  Memory Requests  Memory Limits  AGE
  ---------                  ----                                       ------------  ----------  ---------------  -------------  ---
  kube-system                coredns-sgjbp                              100m (5%)     0 (0%)      70Mi (0%)        170Mi (2%)     3h31m
  kube-system                gravity-site-4wqn2                         0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h30m
  kube-system                log-collector-fc97d699f-wwpls              100m (5%)     500m (25%)  200Mi (2%)       600Mi (7%)     3h29m
  kube-system                log-forwarder-bn7rz                        100m (5%)     500m (25%)  200Mi (2%)       600Mi (7%)     3h31m
  kube-system                tiller-deploy-7f5cd54c97-php5g             0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 grafana-5fd4fdbd85-rvmgv                   0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 heapster-5858fcb487-lpgsz                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 influxdb-7754bf8967-w8c8t                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 kapacitor-9d6954f84-mf4fn                  0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 nethealth-km2d8                            0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h30m
  monitoring                 telegraf-ddbcb564f-5cwfs                   0 (0%)        0 (0%)      0 (0%)           0 (0%)         3h29m
  monitoring                 telegraf-node-master-5tpct                 50m (2%)      100m (5%)   50Mi (0%)        100Mi (1%)     3h30m
  rtf                        agent-5586558cd8-j9bpc                     100m (5%)     1 (50%)     200Mi (2%)       500Mi (6%)     3h28m
  rtf                        cluster-status-1632962400-bwlmb            10m (0%)      100m (5%)   50Mi (0%)        100Mi (1%)     4m13s
  rtf                        mule-clusterip-service-755b6fcbbd-7kt5v    50m (2%)      500m (25%)  100Mi (1%)       500Mi (6%)     3h28m
  rtf                        resource-cache-79dd694fbf-tkvkr            150m (7%)     550m (27%)  100Mi (1%)       350Mi (4%)     3h28m
Allocated resources:
  (Total limits may be over 100 percent, i.e., overcommitted.)
  Resource           Requests     Limits
  --------           --------     ------
  cpu                660m (33%)   3250m (162%)
  memory             970Mi (12%)  2920Mi (38%)
  ephemeral-storage  0 (0%)       0 (0%)

allocatedRequestCapacity refers to the "Requests" column of the "Allocated Resources" section. You will see 660m for CPU and 970Mi for memory. If you add the "CPU Requests" of the pods from the first column of "Non-terminated Pods" (100 + 100 + 100 + 50 + 100 + 10 + 50 +150), this will total 660m. If you add the "Memory Limits" of the pods from the 4th column of "Non-terminated Pods" (70 + 200 + 200 + 50 + 200 + 50 + 100 + 100), this will total 970Mi.

allocatedLimitCapacity  refers to the "Limits" column of the "Allocated Resources" section. You will see 3250m for CPU and 2920Mi for memory. If you add the "CPU Limits" of the pods from the second column of "Non-terminated Pods" (500 + 500 + 100 + 1000 + 100 + 500 + 550), this will total 3250m. If you add the "Memory Requests" of the pods from the 3rd column of "Non-terminated Pods" (170 + 600 + 600 + 100 + 500 + 100 + 500 + 350), this will total 2920Mi.
Número del artículo de conocimiento

001116761

 
Cargando
Salesforce Help | Article