[Bugs] [Bug 1196223] New: gluster brick offline/online (disable/enable) command that does not affect glusterfs client on the same node???

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1196223

            Bug ID: 1196223
           Summary: gluster brick offline/online (disable/enable) command
                    that does not affect glusterfs client on the same
                    node???
           Product: GlusterFS
           Version: mainline
         Component: cli
          Severity: low
          Assignee: bugs at gluster.org
          Reporter: itec at forschungsgruppe.de
                CC: bugs at gluster.org, gluster-bugs at redhat.com



Description of problem:
I would like to enable/disable certain replicated gluster bricks temporarily so
that the glusterfsd process is stopped on disable and started on enable.

This is to be able to manually restart this component without restarting the
whole node. Mounted gluster filesystems (mounted through the gluster client on
the same node) should not be affected as long as sufficient replicas exist on
other nodes.

On enable (online) the brick should be healed. The existing data should not be
erased and replaced. Instead it should be taken as a starting point for the
healing.

Is that possible somehow?

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the assignee for the bug.