[Bugs] [Bug 1436167] New: [Brick Multiplexing]: RFE: Need a backup for brick process with multiplexing to avoid single point of failure

[bugzilla at redhat.com]

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

            Bug ID: 1436167
           Summary: [Brick Multiplexing]: RFE: Need a backup for brick
                    process with multiplexing to avoid single point of
                    failure
           Product: GlusterFS
           Version: 3.10
         Component: core
          Severity: high
          Assignee: bugs at gluster.org
          Reporter: nchilaka at redhat.com
                CC: bugs at gluster.org



Description of problem:
=======================
Currently with brick multiplexing we avoid spawning dedicated process for each
brick hosted on a node.
While this is the theme of brick multiplexing, we need to also make sure a way
to have a backup , can be in the form of process or a different infra so that
one process is not a single point of failure.
For eg: lets say we have 50 volumes, host on a gluster cluster of say 2 nodes
Now, when there is a single brick process for all the bricks in each node.
what if the that process gets,killed? then all the bricks in that node gets
killed.
Instead why not have a HA or replica or some other infra such that there is no
single point of failure. say instead of having 1 process, I can have two
processes which are replica of each other.

In this way we have a high availability and also we have brought down the
number of process from 50 to 2 using Brick multiplexing

Version-Release number of selected component (if applicable):
[root at dhcp35-192 ~]# rpm -qa|grep gluster
glusterfs-libs-3.10.0-1.el7.x86_64
glusterfs-api-3.10.0-1.el7.x86_64
glusterfs-debuginfo-3.10.0-1.el7.x86_64
glusterfs-3.10.0-1.el7.x86_64
glusterfs-fuse-3.10.0-1.el7.x86_64
glusterfs-cli-3.10.0-1.el7.x86_64
glusterfs-rdma-3.10.0-1.el7.x86_64
glusterfs-client-xlators-3.10.0-1.el7.x86_64
glusterfs-server-3.10.0-1.el7.x86_64
[root at dhcp35-192 ~]#

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