-
Enhancement
-
Resolution: Fixed
-
P4
-
13
-
b14
-
generic
-
linux
| Issue | Fix Version | Assignee | Priority | Status | Resolution | Resolved In Build |
|---|---|---|---|---|---|---|
| JDK-8286025 | 11.0.17-oracle | Harold Seigel | P4 | Resolved | Fixed | b01 |
| JDK-8284727 | 11.0.16 | Matthias Baesken | P4 | Resolved | Fixed | b01 |
| JDK-8296053 | 8u371 | Ivan Bereziuk | P4 | Resolved | Fixed | b01 |
In the VM's error log, the container information was dumpped as:
---------------------------------
container (cgroup) information:
container_type: cgroupv1
cpu_cpuset_cpus: 0-11
cpu_memory_nodes: 0
active_processor_count: 12
cpu_quota: -1
cpu_period: 100000
cpu_shares: -1
memory_limit_in_bytes: -1
memory_and_swap_limit_in_bytes: -2
memory_soft_limit_in_bytes: -1
memory_usage_in_bytes: 11690164224
memory_max_usage_in_bytes: 1806413824
---------------------------------
Items such as "memory_limit_in_bytes" and "memory_and_swap_limit_in_bytes" are difficult to understand.
It might be more human-readable if we could dump it like this:
---------------------------------
container (cgroup) information:
container_type: cgroupv1
cpu_cpuset_cpus: 0-11
cpu_memory_nodes: 0
active_processor_count: 12
cpu_quota: no quota
cpu_period: 100000
cpu_shares: no share
memory_limit_in_bytes: unlimited
memory_and_swap_limit_in_bytes: failed
memory_soft_limit_in_bytes: unlimited
memory_usage_in_bytes: 11690164224
memory_max_usage_in_bytes: 1806413824
---------------------------------
---------------------------------
container (cgroup) information:
container_type: cgroupv1
cpu_cpuset_cpus: 0-11
cpu_memory_nodes: 0
active_processor_count: 12
cpu_quota: -1
cpu_period: 100000
cpu_shares: -1
memory_limit_in_bytes: -1
memory_and_swap_limit_in_bytes: -2
memory_soft_limit_in_bytes: -1
memory_usage_in_bytes: 11690164224
memory_max_usage_in_bytes: 1806413824
---------------------------------
Items such as "memory_limit_in_bytes" and "memory_and_swap_limit_in_bytes" are difficult to understand.
It might be more human-readable if we could dump it like this:
---------------------------------
container (cgroup) information:
container_type: cgroupv1
cpu_cpuset_cpus: 0-11
cpu_memory_nodes: 0
active_processor_count: 12
cpu_quota: no quota
cpu_period: 100000
cpu_shares: no share
memory_limit_in_bytes: unlimited
memory_and_swap_limit_in_bytes: failed
memory_soft_limit_in_bytes: unlimited
memory_usage_in_bytes: 11690164224
memory_max_usage_in_bytes: 1806413824
---------------------------------
- backported by
-
JDK-8284727 Improve the readability of container information in the error log
-
- Resolved
-
-
-
- Resolved
-
-
-
- Resolved
-
