Bug 1116168 - RFE: Allow geo-replication to slave Volume in same trusted storage pool
Summary: RFE: Allow geo-replication to slave Volume in same trusted storage pool
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: mainline
Hardware: All
OS: All
medium
medium
Target Milestone: ---
Assignee: Aravinda VK
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-07-03 23:41 UTC by Andrew Hatfield
Modified: 2018-11-19 05:50 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2018-11-19 05:20:08 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github 556 0 None None None 2018-11-19 05:50:01 UTC

Description Andrew Hatfield 2014-07-03 23:41:56 UTC 
Description of problem:

With the new geo-replication we are now unable to configure geo-replication between a Master and Slave Volume on the same Trusted Storage Pool.

There is a valid use-case to allow users to asynchronously geo-replicate Volumes within the same Trusted Storage Pool.

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:20 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 Vijay Bellur 2018-11-19 05:50:01 UTC 
Migrated to github:

https://github.com/gluster/glusterfs/issues/556

Please follow the github issue for further updates on this bug.
Note You need to log in before you can comment on or make changes to this bug.