Bug 762264 (GLUSTER-532) - Request timeout message is shown when one of the node is down
Summary: Request timeout message is shown when one of the node is down
Keywords:
Status: CLOSED WONTFIX
Alias: GLUSTER-532
Product: GlusterSP
Classification: Retired
Component: core
Version: unspecified
Hardware: All
OS: Linux
low
low
Target Milestone: 3.0.5
Assignee: Harshavardhana
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-12 09:06 UTC by Sachidananda Urs
Modified: 2015-03-23 01:03 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed:
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Balamurugan Arumugam 2010-01-12 08:17:43 UTC 
In which list are you getting this error?  Can you tell us reproducer?
Comment 1 Sachidananda Urs 2010-01-12 09:06:53 UTC 
When one of the node is down, none of the servers are shown in the list. `Request timedout' message is shown.
Comment 2 Amar Tumballi 2010-01-12 13:20:59 UTC 
This was happening when two nodes (out of 4) were not reachable. Also, I saw in /tmp/transport.log for a get-server-list command there were no responses (even from the same server). Later, I killed python, and everything started working fine.
Comment 3 Balamurugan Arumugam 2010-01-15 09:42:28 UTC 
This happens when ejabberd crashes abnormally.
Comment 4 Harshavardhana 2010-02-09 14:55:16 UTC 
Proposed handling of this case is to restart ejabberd if it crashes in a "non-stop" loop. Will be available in 3.0.3 release
Comment 5 Harshavardhana 2010-03-11 07:41:23 UTC 
ejabberd is being removed since 3.0.5 release, all ejabberd related bugs are invalid.
Comment 6 Shireesh 2010-11-29 06:43:50 UTC 
Issue with ejabberd - resolved in 3.1.x by removing the dependency on ejabberd
Note You need to log in before you can comment on or make changes to this bug.