Bug 1036661

Summary: dist-geo-rep : gsyncd worker got hung when sshd was stopped in the corresponding slave node.
Product: Red Hat Gluster Storage Reporter: Vijaykumar Koppad <vkoppad>
Component: geo-replicationAssignee: Bug Updates Notification Mailing List <rhs-bugs>
Status: CLOSED EOL QA Contact: storage-qa-internal <storage-qa-internal>
Severity: high Docs Contact:
Priority: medium    
Version: 2.1CC: avishwan, chrisw, csaba, david.macdonald
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1285199 (view as bug list) Environment:
Last Closed: Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On:    
Bug Blocks: 1285199    

Description Vijaykumar Koppad 2013-12-02 12:53:44 UTC 
Description of problem: gsyncd worker got hung while syncing files when sshd was stopped in the corresponding slave node. The geo-rep status was also saying ok , and there were no errors in the logs. It was not syncing anything, just hung in futex

Version-Release number of selected component (if applicable):glusterfs-3.4.0.45geo-1


How reproducible: doesn't happen everytime. 


Steps to Reproduce:
1.create and start a geo-rep relationship between master and slave.
2.start creating data on master.
3.while active gsyncd syncing files to slave, stop sshd on the corresponding slave

Actual results: gsyncd got hung 


Expected results: gsyncd shouldn't hang, it is disastrous.


Additional info:
Comment 3 Aravinda VK 2015-11-25 08:50:18 UTC 
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.
Comment 4 Aravinda VK 2015-11-25 08:51:45 UTC 
Closing this bug since RHGS 2.1 release reached EOL. Required bugs are cloned to RHGS 3.1. Please re-open this issue if found again.