Bug 1944651 - [RFE][Cephadm]: rgw-ha daemon in cephadm should allow choice of RGWs to be covered by HAproxy
Summary: [RFE][Cephadm]: rgw-ha daemon in cephadm should allow choice of RGWs to be co...
Keywords:
Status: CLOSED DUPLICATE of bug 1936887
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Cephadm
Version: 5.0
Hardware: Unspecified
OS: Linux
unspecified
high
Target Milestone: ---
: 5.1
Assignee: Juan Miguel Olmo
QA Contact: Vasishta
Karen Norteman
URL:
Whiteboard:
Depends On:
Blocks: 1895577
TreeView+ depends on / blocked
 
Reported: 2021-03-30 12:04 UTC by Tejas
Modified: 2021-04-01 11:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-04-01 11:30:09 UTC
Embargoed:


Attachments (Terms of Use)

Description Tejas 2021-03-30 12:04:50 UTC
The current ha-proxy keepalive implementation using cephadm uses all available RGWs to be configured as backend , But by design RGW daemons can be part multiple zones , or multiple realms, all of which cannot be covered by the same haproxy daemon.

This design is very limiting in that it can be used only in cases where  all RGW daemons are part of the same zone.

/]# ceph -s
  cluster:
    id:     b8f37602-8c98-11eb-b5c1-fa163eb9cc01
    health: HEALTH_WARN
            7 failed cephadm daemon(s)
 
  services:
    mon: 5 daemons, quorum ceph-tejas-1616579452828-node1-mon-mgr-installer-node-exporter,ceph-tejas-1616579452828-node9-client,ceph-tejas-1616579452828-node6-mon-rgw-node-exporter-crash,ceph-tejas-1616579452828-node5-osd-node-exporter-crash,ceph-tejas-1616579452828-node3-osd-node-exporter-crash (age 4h)
    mgr: ceph-tejas-1616579452828-node1-mon-mgr-installer-node-exporter.rdfiei(active, since 5d), standbys: ceph-tejas-1616579452828-node9-client.spjimk
    osd: 12 osds: 12 up (since 14h), 12 in (since 5d)
    rgw: 7 daemons active (3 hosts, 3 zones)    <--- 3 zones across 2 realms

Comment 1 Tejas 2021-04-01 11:30:09 UTC

*** This bug has been marked as a duplicate of bug 1936887 ***


Note You need to log in before you can comment on or make changes to this bug.