Bug 1028343 - dist-geo-rep: delete operations results in a slave crash
Summary: dist-geo-rep: delete operations results in a slave crash
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: ---
: ---
Assignee: Venky Shankar
QA Contact: Vijaykumar Koppad
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-08 09:13 UTC by Venky Shankar
Modified: 2014-08-25 00:50 UTC (History)
5 users (show)

Fixed In Version: glusterfs-3.4.0.42rhs-1
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-11-27 15:47:06 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2013:1769 0 normal SHIPPED_LIVE Red Hat Storage 2.1 enhancement and bug fix update #1 2013-11-27 20:17:39 UTC

Description Venky Shankar 2013-11-08 09:13:06 UTC
Description of problem:
Delete operations performed on the master results in geo-replication crashing on the slave.


Version-Release number of selected component (if applicable):
glusterfs-3.4.0.40.2

How reproducible:
Always

Steps to Reproduce:
1. Create files on the master
2. Allow the files to be synced to the slave
3. Delete few files from master

Actual results:
Geo-replication crashes on the slave

Expected results:
No crashes, should purge entries on the slave.

Comment 4 Vijaykumar Koppad 2013-11-13 07:28:42 UTC
Tried on the build glusterfs-3.4.0.43rhs-1, it works fine now.

The steps I followed. 

1.create and start a geo-rep relationship between master and slave
2.create files one master and let it sync, ( created reg-files,symlinks, hardlink)
3.delete the files created on the master. 
4.check if it deletes everything.

Comment 5 errata-xmlrpc 2013-11-27 15:47:06 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-1769.html


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