Bug 1709737 - geo-rep: Always uses rsync even with use_tarssh set to true
Summary: geo-rep: Always uses rsync even with use_tarssh set to true
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: geo-replication
Version: 6
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Kotresh HR
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-05-14 08:42 UTC by Kotresh HR
Modified: 2019-05-17 07:49 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-17 07:49:20 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 22724 0 None Merged geo-rep: Fix sync-method config 2019-05-17 07:49:19 UTC

Description Kotresh HR 2019-05-14 08:42:17 UTC
This bug was initially created as a copy of Bug #1707686

I am copying this bug because: 



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:

Comment 1 Worker Ant 2019-05-14 08:53:33 UTC
REVIEW: https://review.gluster.org/22724 (geo-rep: Fix sync-method config) posted (#1) for review on release-6 by Kotresh HR

Comment 2 Worker Ant 2019-05-17 07:49:20 UTC
REVIEW: https://review.gluster.org/22724 (geo-rep: Fix sync-method config) merged (#2) on release-6 by Amar Tumballi


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