Actions
Bug #56415
closedcephadm uses static placement when creating daemons causing a hotspot on the 'root' node
% Done:
0%
Source:
Tags:
Backport:
quincy,pacific
Regression:
No
Severity:
3 - minor
Reviewed:
Description
cephadm uses static placement when creating daemons. As consequence, most of the deamons end up in the first node (the one used to bootstrap the cluster) creating a hotspot on this node. In a cluster of 4 nodes and after creating several daemons right now the result is an unbalanced cluster:
[ceph: root@ceph-node-0 /]# for i in `seq 0 3`; do echo ceph-node-$i; ceph orch ps | grep ceph-node-$i | wc -l; done ceph-node-0 15 ceph-node-1 14 ceph-node-2 4 ceph-node-3 4
cephadm used to distribute the load randomly across the cluster but this was broken by the change: https://github.com/ceph/ceph/commit/adceaa9b28278601c56a7db1c3f42eaa592ec4d1 (introduced as part of the PR https://github.com/ceph/ceph/pull/41007). So all versions containing this change suffer from this issue.
Updated by Redouane Kachach Elhichou almost 2 years ago
- Related to Feature #55879: mgr/cephadm: balanced static placement with rendezvous or consistent hashing added
Updated by Redouane Kachach Elhichou almost 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 46892
Updated by Redouane Kachach Elhichou almost 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56454: quincy: cephadm uses static placement when creating daemons causing a hotspot on the 'root' node added
Updated by Backport Bot almost 2 years ago
- Copied to Backport #56455: pacific: cephadm uses static placement when creating daemons causing a hotspot on the 'root' node added
Updated by Adam King almost 2 years ago
- Status changed from Pending Backport to Resolved
Updated by Redouane Kachach Elhichou almost 2 years ago
- Related to Feature #44255: cephadm: scheduler should consider other daemons on each node added
Actions