mmodzelewski opened a new pull request, #3615: URL: https://github.com/apache/iggy/pull/3615
Shard threads pinned to absolute cores 0..n, silently violating any affinity/cpuset restriction from the parent environment (systemd AllowedCPUs=, container cpusets, taskset): sched_setaffinity to a core outside the allowed set fails with EINVAL. On shared hosts it also piled every process onto the same low-numbered cores while the rest sat idle. Draw pinned cores from the process's allowed CPU set instead, and fail fast when an explicit range names a core outside it. Add pin_cores (default true); set false on multi-tenant hosts to drop pinning entirely so the kernel scheduler places shard threads freely. With a NUMA-aware allocation, false also drops the memory- node bindings and warns, since NUMA placement without pinning is meaningless. Also report cgroup memory limits in shard stats when tighter than the host, so a quota-restricted server reports its real ceiling. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
