Bug 2137837

Summary: [DDF] [MetroDR] When setting this CRUSH rule we are always locating all the primary PGs in DC1. If we have active/active OCP
Product: [Red Hat Storage] Red Hat OpenShift Data Foundation Reporter: Direct Docs Feedback <ddf-bot>
Component: documentationAssignee: Olive Lakra <olakra>
Status: CLOSED CURRENTRELEASE QA Contact: akarsha <akrai>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.11CC: akrai, asriram, ddomingu, dparkes, hnallurv, mbukatov, ocs-bugs, odf-bz-bot, olakra
Target Milestone: ---   
Target Release: ODF 4.12.0   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-02-08 14:12:56 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Direct Docs Feedback 2022-10-26 11:16:33 UTC
When setting this CRUSH rule we are always locating all the primary PGs in DC1. If we have active/active OCP clusters we want to spread the primary PGs in all DCs, not locating the primary PGs in DC1 as all the applications will read from DC1 suffering performance issues.

If you want to spread the primary PGs between DCs, you have to set the following rule:

rule stretch_rule {
        id 1
        type replicated
        min_size 1
        max_size 10
        step take default
        step choose firstn 0 type datacenter
        step chooseleaf firstn 2 type host
        step emit
}

Thanks. Regards

Reported by: ddomingu

https://access.redhat.com/documentation/en-us/red_hat_openshift_data_foundation/4.11/html/configuring_openshift_data_foundation_disaster_recovery_for_openshift_workloads/metro-dr-solution#annotations:9bb3553a-f86b-414e-9df7-bbab730d611c

Comment 14 Olive Lakra 2022-12-01 06:40:07 UTC
*** Bug 2137791 has been marked as a duplicate of this bug. ***

Comment 20 Martin Bukatovic 2022-12-21 17:40:23 UTC
Note that with this change, BZ 2100920 is no longer reproducible in the default Metro DR ceph configuration.