Hi, Might be a dumb question … I'm wondering how I can set those config variables in some but not all RGW processes? I'm on a cephadm 17.2.6. On 3 nodes I have RGWs. The ones on 8080 are behind haproxy for users. the ones one 8081 I'd like for sync only. # ceph orch ps | grep rgw rgw.max.maxvm4.lmjaef maxvm4 *:8080 running (51m) 4s ago 2h 262M - 17.2.6 d007367d0f3c 315f47a4f164 rgw.max.maxvm4.lwzxpf maxvm4 *:8081 running (51m) 4s ago 2h 199M - 17.2.6 d007367d0f3c 7ae82e5f6ef2 rgw.max.maxvm5.syxpnb maxvm5 *:8081 running (51m) 4s ago 2h 137M - 17.2.6 d007367d0f3c c0635c09ba8f rgw.max.maxvm5.wtpyfk maxvm5 *:8080 running (51m) 4s ago 2h 267M - 17.2.6 d007367d0f3c b4ad91718094 rgw.max.maxvm6.ostneb maxvm6 *:8081 running (51m) 4s ago 2h 150M - 17.2.6 d007367d0f3c 83b2af8f787a rgw.max.maxvm6.qfulra maxvm6 *:8080 running (51m) 4s ago 2h 262M - 17.2.6 d007367d0f3c 81d01bf9e21d # ceph config show rgw.max.maxvm4.lwzxpf Error ENOENT: no config state for daemon rgw.max.maxvm4.lwzxpf # ceph config set rgw.max.maxvm4.lwzxpf rgw_enable_lc_threads false Error EINVAL: unrecognized config target 'rgw.max.maxvm4.lwzxpf' (Not surprised) # ceph tell rgw.max.maxvm4.lmjaef get rgw_enable_lc_threads error handling command target: local variable 'poolid' referenced before assignment # ceph tell rgw.max.maxvm4.lmjaef set rgw_enable_lc_threads false error handling command target: local variable 'poolid' referenced before assignment Is there any way to set the config for specific RGWs in a containerized env? (ceph.conf doesn't work. Doesn't do anything and gets overwritten with a minimall version at "unpredictable" intervalls) Thanks for any ideas. Ciao, Uli > On 15. May 2023, at 14:15, Konstantin Shalygin <k0ste@xxxxxxxx> wrote: > > Hi, > >> On 15 May 2023, at 14:58, Michal Strnad <michal.strnad@xxxxxxxxx> wrote: >> >> at Cephalocon 2023, it was mentioned several times that for service tasks such as data deletion via garbage collection or data replication in S3 via zoning, it is good to do them on dedicated radosgw gateways and not mix them with gateways used by users. How can this be achieved? How can we isolate these tasks? Will using dedicated keyrings instead of admin keys be sufficient? How do you operate this in your environment? > > Just: > > # don't put client traffic to "dedicated radosgw gateways" > # disable lc/gc on "gateways used by users" via `rgw_enable_lc_threads = false` & `rgw_enable_gc_threads = false` > > > k > _______________________________________________ > ceph-users mailing list -- ceph-users@xxxxxxx > To unsubscribe send an email to ceph-users-leave@xxxxxxx _______________________________________________ ceph-users mailing list -- ceph-users@xxxxxxx To unsubscribe send an email to ceph-users-leave@xxxxxxx
 |