Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1712223

Summary:	geo-rep: With heavy rename workload geo-rep log if flooded
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	bugs <bugs>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-05-23 11:30:19 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Kotresh HR 2019-05-21 05:12:44 UTC

This bug was initially created as a copy of Bug #1709653

I am copying this bug because: 



Description of problem:
With heavy rename workload as mentioned in bug 1694820, geo-rep log is flooded with gfid conflict resolution logs. All the entries to be fixed are logged at INFO level.

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-rep and run the reproducer given in bug 1694820


Actual results:
Geo-rep log is flooded

Expected results:
Geo-rep log should not be flooded.

Additional info:

Comment 1 Worker Ant 2019-05-21 05:17:31 UTC

REVIEW: https://review.gluster.org/22752 (geo-rep: Convert gfid conflict resolutiong logs into debug) posted (#1) for review on release-6 by Kotresh HR

Comment 2 Worker Ant 2019-05-23 11:30:19 UTC

REVIEW: https://review.gluster.org/22752 (geo-rep: Convert gfid conflict resolutiong logs into debug) merged (#1) on release-6 by Kotresh HR