Bug 1036661 - dist-geo-rep : gsyncd worker got hung when sshd was stopped in the corresponding slave node.
Summary: dist-geo-rep : gsyncd worker got hung when sshd was stopped in the correspond...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: geo-replication
Version: 2.1
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
: ---
Assignee: Bug Updates Notification Mailing List
QA Contact: storage-qa-internal@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 1285199
TreeView+ depends on / blocked
 
Reported: 2013-12-02 12:53 UTC by Vijaykumar Koppad
Modified: 2015-11-25 08:51 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1285199 (view as bug list)
Environment:
Last Closed:
Embargoed:

Attachments (Terms of Use)

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.
Note You need to log in before you can comment on or make changes to this bug.