Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
---|---|---|---|---|---|---|
JDK-8183680 | 8u161 | Gustavo Romero | P4 | Resolved | Fixed | b01 |
JDK-8181462 | 8u152 | Gustavo Romero | P4 | Resolved | Fixed | b05 |
JDK-8192241 | emb-8u161 | Gustavo Romero | P4 | Resolved | Fixed | b01 |
topology:
available: 4 nodes (0-1,16-17)
node 0 cpus: 0 8 16 24 32
node 0 size: 130706 MB
node 0 free: 145 MB
node 1 cpus: 40 48 56 64 72
node 1 size: 0 MB
node 1 free: 0 MB
node 16 cpus: 80 88 96 104 112
node 16 size: 130630 MB
node 16 free: 529 MB
node 17 cpus: 120 128 136 144 152
node 17 size: 0 MB
node 17 free: 0 MB
node distances:
node 0 1 16 17
0: 10 20 40 40
1: 20 10 40 40
16: 40 40 10 20
17: 40 40 20 10
Also, some nodes can also be present in the topology but contain no memory (a memory-less node in libnuma terms).
- backported by
-
JDK-8181462 PPC64: "mbind: Invalid argument" when -XX:+UseNUMA is used
-
- Resolved
-
-
JDK-8183680 PPC64: "mbind: Invalid argument" when -XX:+UseNUMA is used
-
- Resolved
-
-
JDK-8192241 PPC64: "mbind: Invalid argument" when -XX:+UseNUMA is used
-
- Resolved
-
-
JDK-8180500 PPC64: "mbind: Invalid argument" when -XX:+UseNUMA is used
-
- Closed
-
- relates to
-
JDK-8181196 Update all JVM NUMA prototypes to use the new NUMA API version 2
-
- Open
-
-
JDK-8163796 'mbind: Invalid argument' when initializing NUMA with small initial heap and large page
-
- Open
-
-
JDK-8181055 PPC64: "mbind: Invalid argument" still seen after 8175813
-
- Resolved
-
-
JDK-8198794 Hotspot crash on Cassandra 3.11.1 startup with libnuma 2.0.3
-
- Closed
-