replica count documentation

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



My understanding is that the file you are writing to is replicated
> accross "n" number of glusterfs servers. You define that "n" when
> creating volume.


This is what I thought as well. But at what kind of consistency level? How
many replicas is the file written to before returning to the client
application? Assuming I have my replica count set to 2 with my 2 brick
setup, it sure isn't strict. I've waited 15 mins after the write to one
brick has finished before it was actually synced up on the second.


Try volume info command to see the replicas.


I'm not so much trying to "see the replicas" as get the number of replicas.
My understanding is that replica != brick, so where is the number of
replicas in the output below?

# gluster volume info virt-isos

Volume Name: virt-isos
Type: Replicate
Status: Started
Number of Bricks: 2
Transport-type: tcp
Bricks:
Brick1: 192.168.0.150:/virt-isos
Brick2: 192.168.0.151:/virt-isos
virt1:~#

Craig Younkins


On Wed, Apr 13, 2011 at 7:17 PM, Mohit Anchlia <mohitanchlia at gmail.com>wrote:

> My understanding is that the file you are writing to is replicated
> accross "n" number of glusterfs servers. You define that "n" when
> creating volume.
>
> Try volume info command to see the replicas.
>
> On Wed, Apr 13, 2011 at 4:14 PM, Craig Younkins <cyounkins at gmail.com>
> wrote:
> > So these are probably dumb questions but I cannot find them anywhere in
> the
> > documentation.
> >
> > What exactly does the replica count paramater to the volume create
> command
> > mean? How many bricks each block is replicated to?
> >
> > How does one query for the replica count of a volume?
> >
> > Thanks!
> >
> > Craig Younkins
> >
> > _______________________________________________
> > Gluster-users mailing list
> > Gluster-users at gluster.org
> > http://gluster.org/cgi-bin/mailman/listinfo/gluster-users
> >
> >
>


[Index of Archives]     [Gluster Development]     [Linux Filesytems Development]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux