Bug 1458113 - Brick Multiplexing: Deleting brick directories of the base volume must gracefully detach from glusterfsd without impacting other volumes IO(currently seeing transport end point error)
Summary: Brick Multiplexing: Deleting brick directories of the base volume must gracef...
Keywords:
Status: CLOSED EOL
Alias: None
Product: GlusterFS
Classification: Community
Component: core
Version: 3.11
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard: brick-multiplexing
Depends On: 1451598 1453977
Blocks: 1444926
TreeView+ depends on / blocked
 
Reported: 2017-06-02 04:54 UTC by Mohit Agrawal
Modified: 2018-06-20 18:28 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1451598
Environment:
Last Closed: 2018-06-20 18:28:28 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)

Comment 1 Worker Ant 2017-06-02 05:20:47 UTC 
REVIEW: https://review.gluster.org/17449 (glusterfs: Not able to mount running volume after enable brick mux and stopped any volume) posted (#1) for review on release-3.11 by MOHIT AGRAWAL (moagrawa)
Comment 2 Worker Ant 2017-06-02 05:45:29 UTC 
REVIEW: https://review.gluster.org/17449 (glusterfs: Not able to mount running volume after enable brick mux and stopped any volume) posted (#2) for review on release-3.11 by MOHIT AGRAWAL (moagrawa)
Comment 3 Worker Ant 2017-06-02 06:15:33 UTC 
REVIEW: https://review.gluster.org/17449 (glusterfs: Not able to mount running volume after enable brick mux and stopped any volume) posted (#3) for review on release-3.11 by MOHIT AGRAWAL (moagrawa)
Comment 4 Worker Ant 2017-06-12 03:18:25 UTC 
REVIEW: https://review.gluster.org/17449 (glusterfs: Not able to mount running volume after enable brick mux and stopped any volume) posted (#4) for review on release-3.11 by MOHIT AGRAWAL (moagrawa)
Comment 5 Shyamsundar 2018-06-20 18:28:28 UTC 
This bug reported is against a version of Gluster that is no longer maintained
(or has been EOL'd). See https://www.gluster.org/release-schedule/ for the
versions currently maintained.

As a result this bug is being closed.

If the bug persists on a maintained version of gluster or against the mainline
gluster repository, request that it be reopened and the Version field be marked
appropriately.
Note You need to log in before you can comment on or make changes to this bug.