Bug 1467510 - protocol/server: Reject the connection if the graph is not ready
Summary: protocol/server: Reject the connection if the graph is not ready
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: GlusterFS
Classification: Community
Component: protocol
Version: mainline
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mohammed Rafi KC
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-07-04 05:59 UTC by Mohammed Rafi KC
Modified: 2019-05-11 11:39 UTC (History)
2 users (show)

Fixed In Version: glusterfs-6.x
Clone Of:
Environment:
Last Closed: 2019-05-11 11:39:45 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Description Mohammed Rafi KC 2017-07-04 05:59:01 UTC 
Description of problem:

We are accepting new connections even though the graph is not ready.


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. Create a volume and start it
2. as soon as the volume is started, start the client also.
3. the connections will be accepted, even when there is no child up event

Actual results:

it just logs and continue

Expected results:

it should fail

Additional info:
Comment 1 Worker Ant 2017-07-04 05:59:22 UTC 
REVIEW: https://review.gluster.org/17686 (protocol/server: reject the connection if graph is not ready) posted (#1) for review on master by mohammed rafi  kc (rkavunga)
Comment 2 Worker Ant 2017-07-09 05:24:52 UTC 
REVIEW: https://review.gluster.org/17686 (protocol/server: reject the connection if graph is not ready) posted (#2) for review on master by Atin Mukherjee (amukherj)
Comment 3 Amar Tumballi 2018-10-08 17:12:16 UTC 
As part of the improvements in cleanup sequence, this is now added in glusterfs master!

GlusterFS-6 would have these fixes.
Note You need to log in before you can comment on or make changes to this bug.