[Bugs] [Bug 1708067] New: geo-rep: Always uses rsync even with use_tarssh set to true

[bugzilla at redhat.com]

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

            Bug ID: 1708067
           Summary: geo-rep: Always uses rsync even with use_tarssh set to
                    true
           Product: Red Hat Gluster Storage
           Version: rhgs-3.5
            Status: NEW
         Component: geo-replication
          Assignee: sunkumar at redhat.com
          Reporter: khiremat at redhat.com
        QA Contact: rhinduja at redhat.com
                CC: avishwan at redhat.com, bugs at gluster.org,
                    csaba at redhat.com, khiremat at redhat.com,
                    rhs-bugs at redhat.com, sankarshan at redhat.com,
                    storage-qa-internal at redhat.com
        Depends On: 1707686
  Target Milestone: ---
    Classification: Red Hat



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

Description of problem:
It always uses rsync to sync data even though use_tarssh is set to true.

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

How reproducible:
Always

Steps to Reproduce:
1. Setup geo-rep between two gluster volumes and start it
2. Set use_tarssh to true
3. Write a huge file on master
4. ps -ef | egrep "tar|rsync" while the big file is syncing to slave.

It show rsync process instead of tar over ssh

Actual results:
use_tarssh has not effect on sync-engine. It's always using rsync.

Expected results:
use_tarssh should use tarssh and not rsync


Additional info:

--- Additional comment from Worker Ant on 2019-05-09 05:18:48 UTC ---

REVIEW: https://review.gluster.org/22683 (geo-rep: Fix sync-method config)
merged (#4) on master by Sunny Kumar


Referenced Bugs:

https://bugzilla.redhat.com/show_bug.cgi?id=1707686
[Bug 1707686] geo-rep: Always uses rsync even with use_tarssh set to true
-- 
You are receiving this mail because:
You are on the CC list for the bug.