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

Bug 1707686

Summary:	geo-rep: Always uses rsync even with use_tarssh set to true
Product:	[Community] GlusterFS	Reporter:	Kotresh HR <khiremat>
Component:	geo-replication	Assignee:	Kotresh HR <khiremat>
Status:	CLOSED NEXTRELEASE	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	mainline	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:
Clones:	1708067 (view as bug list)		Environment:
Last Closed:	2019-05-09 05:18:48 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1708067

Description Kotresh HR 2019-05-08 05:34:05 UTC

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-09 05:18:48 UTC

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