Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1695425 - [goe-rep]: Checksum mismatch when 2x2 /arbiter vols are converted [NEEDINFO]
Summary: [goe-rep]: Checksum mismatch when 2x2 /arbiter vols are converted
Keywords:
Status: MODIFIED
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat
Component: Documentation
Version: rhgs-3.4
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Srijita Mukherjee
QA Contact: Rahul Hinduja
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-04-03 05:29 UTC by Rochelle
Modified: 2019-04-15 06:19 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
khiremat: needinfo? (rallan)
lbailey: needinfo? (khiremat)


Attachments (Terms of Use)

Description Rochelle 2019-04-03 05:29:36 UTC
Description of problem:
========================
Filing this doc BZ to document issue raised at :
https://bugzilla.redhat.com/show_bug.cgi?id=1683893

The work around to be documented is :

IF the brick to be added is from a new node, which is already in the cluster while creating the original geo-rep session even if the node was not used.(Not newly added)
**Before adding the brick**
1. Disable 'use_meta_volume' geo-rep option
#gluster volume geo-replication <mastervol> <slavehost>::<slavevol> config use_meta_volume false 

2. Add brick at master/slave
The newly added brick in the session will be in "created" state so use the "start force" option
#gluster volume geo-rep <mastervol> <slavehost>::<slavevol> start force

3. Wait for self heal to complete on the newly added brick
4. Set geo-rep checkpoint 
gluster volume geo-rep <mastervol> <slavehost>::<slavevol> config checkpoint now

5. Check whether the checkpoint is met:
#gluster volume geo-rep <mastervol> <slavehost>::<slavevol> status detail

6. Re-enable 'use_meta_volume' option once the checkpoint is met
#gluster volume geo-rep <mastervol> <slavehost>::<slavevol> config use_meta_volume true


If the node was not already in the cluster before creating the original session, 
you will need to follow the steps already mentioned in the guide for adding a brick from a new node.


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