Displaying 4 results from an estimated 4 matches for "885g".
Did you mean:
8853
2018 Feb 27
2
Quorum in distributed-replicate volume
...luster.server-quorum-type: server
features.shard: on
cluster.data-self-heal-algorithm: full
storage.owner-uid: 64055
storage.owner-gid: 64055
For brick sizes, saruman/gandalf have
$ df -h /var/local/brick0
Filesystem Size Used Avail Use% Mounted on
/dev/mapper/gandalf-gluster 885G 55G 786G 7% /var/local/brick0
and the other four have
$ df -h /var/local/brick0
Filesystem Size Used Avail Use% Mounted on
/dev/sdb1 11T 254G 11T 3% /var/local/brick0
--
Dave Sherohman
2018 Feb 27
0
Quorum in distributed-replicate volume
...d: on
> cluster.data-self-heal-algorithm: full
> storage.owner-uid: 64055
> storage.owner-gid: 64055
>
>
> For brick sizes, saruman/gandalf have
>
> $ df -h /var/local/brick0
> Filesystem Size Used Avail Use% Mounted on
> /dev/mapper/gandalf-gluster 885G 55G 786G 7% /var/local/brick0
>
> and the other four have
>
> $ df -h /var/local/brick0
> Filesystem Size Used Avail Use% Mounted on
> /dev/sdb1 11T 254G 11T 3% /var/local/brick0
>
If you want to use the first two bricks as arbiter, then you need to be
a...
2018 Feb 27
0
Quorum in distributed-replicate volume
On Mon, Feb 26, 2018 at 6:14 PM, Dave Sherohman <dave at sherohman.org> wrote:
> On Mon, Feb 26, 2018 at 05:45:27PM +0530, Karthik Subrahmanya wrote:
> > > "In a replica 2 volume... If we set the client-quorum option to
> > > auto, then the first brick must always be up, irrespective of the
> > > status of the second brick. If only the second brick is up,
2018 Feb 26
2
Quorum in distributed-replicate volume
On Mon, Feb 26, 2018 at 05:45:27PM +0530, Karthik Subrahmanya wrote:
> > "In a replica 2 volume... If we set the client-quorum option to
> > auto, then the first brick must always be up, irrespective of the
> > status of the second brick. If only the second brick is up, the
> > subvolume becomes read-only."
> >
> By default client-quorum is