Bug 915996

Summary: [RFE] Cascading Geo-Replication Weighted Routes
Product: [Community] GlusterFS Reporter: Ben Stromski <benjamin.stromski>
Component: geo-replicationAssignee: bugs <bugs>
Status: CLOSED EOL QA Contact:
Severity: unspecified Docs Contact:
Priority: low    
Version: mainlineCC: avishwan, bugs, gluster-bugs, rwheeler
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-10-22 15:46:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Ben Stromski 2013-02-26 23:47:16 UTC
Description of problem:
Would love to have the ability to weight routes / nodes within a geo-replicated schema -- i.e. have the client be aware of its closest slave to read from, and if that slave goes down, fail over to the next closest slave down the line.

Our overall topology will appear as follows:
(2) Master Nodes -> (2) Regional Slaves -> (2) Co-location Slaves <- Clients

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Niels de Vos 2014-11-27 14:45:14 UTC
Feature requests make most sense against the 'mainline' release, there is no ETA for an implementation and requests might get forgotten when filed against a particular version.

Comment 2 Kaleb KEITHLEY 2015-10-22 15:46:38 UTC
because of the large number of bugs filed against mainline version\ is ambiguous and about to be removed as a choice.

If you believe this is still a bug, please change the status back to NEW and choose the appropriate, applicable version for it.