I can't remember seeing this before. What does `ceph orch ls mon --export` and `ceph orch host ls` give in the cluster at this point? I wonder if there was an issue with applying the spec file.
On Thu, Jul 18, 2024 at 7:33 AM Yonatan Zaken <yzaken@xxxxxxxxxx> wrote:
Hi All,_______________________________________________
Working with ceph reef (18.2.2) release, has anyone experienced a scenario where after Ceph cluster deployment
an extra mon daemon appeared on a random node?
E.g. for the following spec:
========================================
---
addr: 172.2.2.112
hostname: controller-0
labels:
- mon
- _admin
- mgr
service_type: host
---
addr: 172.2.2.113
hostname: storage-0
labels:
- osd
service_type: host
---
addr: 172.31.2.110
hostname: storage-1
labels:
- osd
service_type: host
---
addr: 172.31.0.161
hostname: storage-2
labels:
- osd
service_type: host
---
addr: 172.31.3.199
hostname: compute-0
labels:
- osd
service_type: host
---
placement:
hosts:
- controller-0
service_id: mon
service_name: mon
service_type: mon
---
placement:
hosts:
- controller-0
service_id: mgr
service_name: mgr
service_type: mgr
---
... osd specfication ...
---
========================================
After running: ceph orch apply -i ceph_spec.yaml
And ceph -s shows:
cluster:
id: 6032c49f-67bf-52b0-be73-40de6801bd1d
health: HEALTH_OK
services:
mon: 2 daemons, quorum controller-0, storage-0 (age 28m)
mgr: overcloud-controller-vcbis-0.fipmna(active, since 39m)
osd: 10 osds: 10 up (since 27m), 10 in (since 27m)
data:
pools: 1 pools, 1 pgs
objects: 2 objects, 449 KiB
usage: 666 MiB used, 415 GiB / 416 GiB avail
pgs: 1 active+clean
Does it make sense that an extra mon daemon appeared on the storage-0 node
even though it wasn't labeled with "mon" ?
Dev mailing list -- dev@xxxxxxx
To unsubscribe send an email to dev-leave@xxxxxxx
_______________________________________________ Dev mailing list -- dev@xxxxxxx To unsubscribe send an email to dev-leave@xxxxxxx
