Skip to content
This repository has been archived by the owner on Mar 26, 2020. It is now read-only.

Fix spurious socket connect failure issue in brick multiplexing stop code path #1468

Open
atinmu opened this issue Jan 8, 2019 · 1 comment
Open

Fix spurious socket connect failure issue in brick multiplexing stop code path #1468

atinmu opened this issue Jan 8, 2019 · 1 comment
Assignees
@atinmu @vpandey-RH
Labels
brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature in progress priority: high

Comments

@atinmu
Copy link
Contributor

atinmu commented Jan 8, 2019

While sending parallel volume requests some of the volume stop operations were failing with the brick socket file reporting EOF.
atinmu pushed a commit to atinmu/glusterd2 that referenced this issue Jan 8, 2019
brick-mux : fix spurious socket connect failure issue during volume stop
1a04cf3 
Change the logic of using the parent socket file to send the detach
request by picking it up from /proc/<pid>/cmdline where pid is the
process id of the parent brick. During Multiplex, this would avoid
creating a hard link of a socket file.

Credits : [email protected] for helping with the utility function

Fixes: gluster#1468
Signed-off-by: Atin Mukherjee <[email protected]>
@atinmu atinmu mentioned this issue Jan 8, 2019
Open
@atinmu atinmu self-assigned this Jan 8, 2019
@atinmu atinmu added in progress GCS/1.0 Issue is blocker for Gluster for Container Storage brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature and removed bug GCS/0.5 GCS 0.5 release labels Jan 9, 2019
@atinmu atinmu removed the GCS/1.0 Issue is blocker for Gluster for Container Storage label Jan 17, 2019
@atinmu
Copy link
Contributor Author

atinmu commented Jan 17, 2019

Taking this out from GCS/1.0 tag considering we're not going to make brick multiplexing a default option in GCS/1.0 release.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@atinmu atinmu

@vpandey-RH vpandey-RH

Labels
brick-multiplexing-issue tracker label to capture all issues related to brick multiplexing feature in progress priority: high
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@atinmu @vpandey-RH