Bug 1712223 - geo-rep: With heavy rename workload geo-rep log if flooded
Summary: geo-rep: With heavy rename workload geo-rep log if flooded
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: bugs@gluster.org
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-21 05:12 UTC by Kotresh HR
Modified: 2019-05-23 11:30 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-23 11:30:19 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 22752 0 None Merged geo-rep: Convert gfid conflict resolutiong logs into debug 2019-05-23 11:30:18 UTC

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
Note You need to log in before you can comment on or make changes to this bug.