Hi,
I just updated almost all storage domains with backup-volfile-servers mount
options, the last one remaining is the hosted_storage domain which serves
hosted engine VM. I wonder if this domain also needs to be configured
with backup-volfile-servers
option? If so how to do this - I can't put
The backup-volfile-servers as an additional mount option should handle the
case where one of the servers goes down - storage domain should continue to
be available.
The servers specified for this option can be the servers participating in
your volume. For instance, the set of unique servers from
We did use the backup-volfile-servers option but still had trouble. We
were simply adding all servers in the cluster as backups, is there a best
practice that should be followed?
On Tue, Dec 12, 2017 at 8:59 AM, Artem Tambovskiy <
artem.tambovs...@gmail.com> wrote:
> I did exactly the same
I did exactly the same mistake with my standalone GlusterFS cluster and now
need to take down all Storage Domains in order to fix this mistake.
Probably, worth to add a few words about this in Installation guide!
On Tue, Dec 12, 2017 at 4:52 PM, Simone Tiraboschi
wrote:
>
>
On Mon, Dec 11, 2017 at 8:44 PM, Beau Sapach wrote:
> We've been doing some experimenting with gluster, and have built a
> stand-alone gluster cluster (not managed by oVirt). We've been able to
> create a storage domain backed by that gluster cluster and run VMs with
>
We've been doing some experimenting with gluster, and have built a
stand-alone gluster cluster (not managed by oVirt). We've been able to
create a storage domain backed by that gluster cluster and run VMs with
their disks on that storage.
The problem we have is that when we take a gluster node
6 matches
Mail list logo