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:
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.
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.