Bug 1243325 - Addiing servers to the trusted storage pool should have a note for geo-rep
Summary: Addiing servers to the trusted storage pool should have a note for geo-rep
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: doc-Administration_Guide
Version: rhgs-3.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: RHGS 3.1.0
Assignee: Divya
QA Contact: Aravinda VK
URL:
Whiteboard:
Depends On:
Blocks: 1202842
TreeView+ depends on / blocked
 
Reported: 2015-07-15 08:34 UTC by Rahul Hinduja
Modified: 2017-11-17 05:20 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-11-17 05:15:46 UTC
Embargoed:


Attachments (Terms of Use)

Description Rahul Hinduja 2015-07-15 08:34:25 UTC
Document URL:
=============

https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3/html-single/Administration_Guide/index.html#Adding_Servers_to_the_Trusted_Storage_Pool

Section Number and Name: 
========================

5.1. Adding Servers to the Trusted Storage Pool

Describe the issue: 
===================

In this section we describe how to add a node to the cluster using "peer probe". But if the existing cluster has a running geo-rep session and if new node is added later. All the geo-rep stop/start/pause/resume cli's will fail because the state is not present on the newly added node.

Suggestions for improvement: 
============================

We should have a NOTE section something like:

Note: If the existing cluster has a geo-replication session then after adding the new node to cluster execute "gluster volume geo-replication <master-vol> <slave-host>::<slave-vol> create push-pem force" from the original master node participating in geo-rep creation with slave node. 

Additional information:

Comment 2 Divya 2015-07-16 10:10:34 UTC
Rahul,

We already have a section "12.5.1. Starting Geo-replication for a New Brick on a New Node" in geo-rep chapter for this scenario http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-Administration_Guide%20%28html-single%29/lastStableBuild/artifact/tmp/en-US/html-single/index.html#Starting_Geo-replication_for_a_New_Brick_on_a_New_Node.

Please confirm if we still need the Note.

Comment 3 Rahul Hinduja 2015-07-21 07:02:55 UTC
Divya,

The section 12.5.1 is specific to expanding the volume having geo-rep when new node is added. 

The issue is specific to expanding the cluster having geo-rep. When may not choose to expand the existing volume by adding a node to cluster. New node can be used to have new volumes in same cluster. Hence we need the proper note in the section 5.1 which is expanding the current cluster.

Comment 5 Rahul Hinduja 2015-07-24 16:07:19 UTC
Verified by running the steps mentioned in the doc. Stop/Start works and document looks good to me. Moving this bug to verified state.


Note You need to log in before you can comment on or make changes to this bug.