Przemyslaw, I think kernel.pid_max can be explained by the ceph-osd config option 'sysctl'. I'm not sure about the others.
sysctl:
type: string
default: '{ kernel.pid_max : 2097152, vm.max_map_count : 524288, kernel.threads-max: 2097152 }'
description: |
YAML-formatted associative array of sysctl key/value pairs to be set
persistently. By default we set pid_max, max_map_count and
threads-max to a high value to avoid problems with large numbers (>20)
of OSDs recovering. very large clusters should set those values even
higher (e.g. max for kernel.pid_max is 4194303).
Przemyslaw, I think kernel.pid_max can be explained by the ceph-osd config option 'sysctl'. I'm not sure about the others.
sysctl:
kernel. threads- max: 2097152 }' formatted associative array of sysctl key/value pairs to be set
type: string
default: '{ kernel.pid_max : 2097152, vm.max_map_count : 524288,
description: |
YAML-
persistently. By default we set pid_max, max_map_count and
threads-max to a high value to avoid problems with large numbers (>20)
of OSDs recovering. very large clusters should set those values even
higher (e.g. max for kernel.pid_max is 4194303).