Bug 763369 (GLUSTER-1637) - replicate should wind reads into read-child only if it is up
Summary: replicate should wind reads into read-child only if it is up
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: GLUSTER-1637
Product: GlusterFS
Classification: Community
Component: replicate
Version: mainline
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Raghavendra G
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-18 08:47 UTC by Raghavendra G
Modified: 2015-12-01 16:45 UTC (History)
2 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 Vijay Bellur 2010-09-18 06:14:26 UTC 
PATCH: http://patches.gluster.com/patch/4854 in master (cluster/replicate: stack_wind into read_child only if it is up.)
Comment 1 Raghavendra G 2010-09-18 08:47:47 UTC 
Though it continues to read from other children, its only done after the read from read-child has failed. If we check whether the read-child is up before we do stack-wind, we can avoid the overhead of first read (which anyways fails).
Comment 2 Amar Tumballi 2010-10-04 04:35:39 UTC 
Please update the bug with current status
Note You need to log in before you can comment on or make changes to this bug.