Bug 765068 (GLUSTER-3336) - Best practices for running geo-rep on multiple volumes
Summary: Best practices for running geo-rep on multiple volumes
Keywords:
Status: CLOSED WORKSFORME
Alias: GLUSTER-3336
Product: Gluster-Documentation
Classification: Community
Component: Other
Version: unspecified
Hardware: x86_64
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Divya
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-08-04 18:40 UTC by Vikas Gorur
Modified: 2012-05-18 11:29 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-05-18 11:29:46 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Vikas Gorur 2011-08-04 18:40:43 UTC 
This is in reference to the admin guide, section 9.5, best practices for geo-replication:

The section assumes that the user is working with only a single Gluster volume. It might be worthwhile to point out that if there are multiple volumes, the user can run geo-rep for them from different servers. It is only necessary that for a *given* volume all commands are run from the same server.
Comment 1 Divya 2012-05-18 11:29:46 UTC 
We have mentioned "It is advisable to run the geo-replication commands in one of the bricks in the trusted storage pool". We have documented it clearly that one of the bricks in the trusted storage pool. Trust storage pool means multiple volumes.
Note You need to log in before you can comment on or make changes to this bug.