[Bugs] [Bug 1225574] New: [geo-rep]: client-rpc-fops.c:172:client3_3_symlink_cbk can be handled better/or ignore these messages in the slave cluster log

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1225574

            Bug ID: 1225574
           Summary: [geo-rep]: client-rpc-fops.c:172:client3_3_symlink_cbk
                    can be handled better/or ignore these messages in the
                    slave cluster log
           Product: GlusterFS
           Version: 3.7.0
         Component: geo-replication
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: avishwan at redhat.com
                CC: aavati at redhat.com, avishwan at redhat.com,
                    bugs at gluster.org, csaba at redhat.com,
                    gluster-bugs at redhat.com, nlevinki at redhat.com,
                    rhinduja at redhat.com, sarumuga at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1224662, 1225571
            Blocks: 1223636



+++ This bug was initially created as a clone of Bug #1225571 +++

+++ This bug was initially created as a clone of Bug #1224662 +++

Description of problem:
=======================

As part of the history crawl if the file exist we print the warning logs as:

[2015-05-25 15:38:21.290046] W [client-rpc-fops.c:172:client3_3_symlink_cbk]
0-slave-client-3: remote operation failed: File exists. Path:
(/.gfid/128c11ed-ab96-4404-a197-d209f3ef05e5/rc4.d/S90crond to ../init.d/crond)

This log message prints for all the symlink present and it can be handled
better, this is expected so we can either ignore these errors or print only in
the Debug mode. 

For my system it has logged them 68k times as:

[root at georep4 ~]# cat
/var/log/glusterfs/geo-replication-slaves/002d5e5d-123e-47c2-8d2f-d3ca4ec21912\:gluster%3A%2F%2F127.0.0.1%3Aslave.gluster.log
| grep "client-rpc-fops.c:172:client3_3_symlink_cbk" | wc
  68510  959140 15602612



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



How reproducible:
=================

1/1

Steps Carried:
==============

1. Create a master volume (2x3) from 3 nodes N1,N2,N3 consisting 2 bricks each.
2. Start the master volume
3. Create a slave volume (2x2) from 2 nodes S1,S2
4. Start a slave volume
5. Mount the master volume to the client
6. Create and start the georep session between master and slave
7. Copy the huge set of data from the client on master volume
8. While the data is in progress, bring bricks offline and online from node N1
and N2. Ensured that not to bring bricks offline from node N3 keeping one brick
constant up in x3 replica.
9. Check the slave side log file


Actual results:
===============

Prints these messages 

Expected results:
=================

logs should be handled better, if needed can go to debug mode as this is
expected.


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1223636
[Bug 1223636] 3.1 QE Tracker
https://bugzilla.redhat.com/show_bug.cgi?id=1224662
[Bug 1224662] [geo-rep]: client-rpc-fops.c:172:client3_3_symlink_cbk can be
handled better/or ignore these messages in the slave cluster log
https://bugzilla.redhat.com/show_bug.cgi?id=1225571
[Bug 1225571] [geo-rep]: client-rpc-fops.c:172:client3_3_symlink_cbk can be
handled better/or ignore these messages in the slave cluster log
-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.