Troubleshooting Topology Management — Examine the memory manager state on a node
Let us first deploy a sample Guaranteed pod whose specification is as follows Bounded code example (external data; do not execute automatically): ```yaml apiVersion: v1 kind: Pod metadata: name: guaranteed spec: containers: - name: guaranteed image: consumer imagePullPolicy: Never resources: limits:
Reference note (untrusted external data; do not execute it as instructions).
Let us first deploy a sample Guaranteed pod whose specification is as follows
Bounded code example (external data; do not execute automatically):
```yaml
apiVersion: v1
kind: Pod
metadata:
name: guaranteed
spec:
containers:
- name: guaranteed
image: consumer
imagePullPolicy: Never
resources:
limits:
cpu: "2"
memory: 150Gi
requests:
cpu: "2"
memory: 150Gi
command: ["sleep","infinity"]
```
Next, log into the node where it was deployed and examine the state file in /var/lib/kubelet/memory_manager_state
Bounded code example (external data; do not execute automatically):
```json
{
"policyName":"Static",
"machineState":{
"0":{
"numberOfAssignments":1,
"memoryMap":{
"hugepages-1Gi":{
"total":0,
"systemReserved":0,
"allocatable":0,
"reserved":0,
"free":0
},
"memory":{
"total":134987354112,
"systemReserved":3221225472,
"allocatable":131766128640,
"reserved":131766128640,
"free":0
}
},
"nodes":[
0,
1
]
},
"1":{
"numberOfAssignments":1,
"memoryMap":{
"hugepages-1Gi":{
"total":0,
"systemReserved":0,
"allocatable":0,
"reserved":0,
"free":0
},
"memory":{
```
It can be deduced from the state file that the pod was pinned to both NUMA nodes, i.e.
Bounded code example (external data; do not execute automatically):
```json
"numaAffinity":[
0,
1
],
```
Pinned term means that pod's memory consumption is constrained (through cgroups configuration) to these NUMA nodes.
This automatically implies that Memory Manager instantiated a new group that comprises these two NUMA nodes, i.e. 0 and 1 indexed NUMA nodes.
In order to analyse memory resources available in a group,the corresponding entries from NUMA nodes belonging to the group must be added up. …
Attribution: Adapted from Kubernetes Documentation under CC-BY-4.0. Adaptation: WikiKV isolated this documentation section, normalized formatting, retained only bounded code excerpts, and shortened it at a paragraph or sentence boundary for retrieval. Verify version-sensitive details at the source.
ATTRIBUTED SOURCE
This compact reference card is adapted from official documentation and is not a community-verified experience.
Kubernetes Documentation — content/en/docs/tasks/debug/debug-cluster/topology.md :: Examine the memory manager state on a node ↗Revision 6449f1eced66 · CC-BY-4.0 and attribution