Hi,
I have a 3 node gluster setup running with one brick exported, /gv0
Centos 7
[root@glusterp1 ganesha]# rpm -aq |grep gluster
glusterfs-client-xlators-3.8.4-1.el7.x86_64
nfs-ganesha-gluster-2.3.3-1.el7.x86_64
glusterfs-3.8.4-1.el7.x86_64
glusterfs-cli-3.8.4-1.el7.x86_64
hi,
These messages generally come when gluster identifies a file needs
heal. May be you should find out why heal traffic is increasing?
On Tue, Oct 11, 2016 at 10:36 PM, Leung, Alex (398C) <
alex.le...@jpl.nasa.gov> wrote:
> Got a tons of error messages from the export-gfs.log, any ideas
>
> Just to check I have this straight:
> - Proxmox cluster using GlusterFS for storage
> - bricks on Proxmox nodes
> - Linux VM's running on Proxmox Nodes
> - InnoDB running on the linux vms
>
Yes, that's exactly it.
> When one of the proxmox nodes crashes (Power outage?) the InnoDB
>
>cleanly handle the sudden shutdown as well as a physical server would, but
>do you know why you are having stability issues to begin with in the
>VM's?A Unless my gluster storage was having some bug issue and oVirt
Oh I know exactly what the stability problem is, the servers are
On 10/10/2016 11:30 PM, Kevin Lemonnier wrote:
We have a few Proxmox clusters using GlusterFS as storage.
The nodes are both running the gluster brick and proxmox,
and one of the problems we have often is that when a server
crashes for some reason, the InnoDB of the VM that were
running on the
On Wed, Oct 12, 2016 at 6:39 AM, Kevin Lemonnier
wrote:
> >
> > imho GlusterFS is not the best place for MySQL.
> >
> > Maybe you want to consider using Galera Cluster with Maxscale.
> >
>
> No, the point isn't to replicate MySQL. It's to have highly available
> VMs that
>
> imho GlusterFS is not the best place for MySQL.
>
> Maybe you want to consider using Galera Cluster with Maxscale.
>
No, the point isn't to replicate MySQL. It's to have highly available
VMs that happens to be running MySQL servers, but they aren't clustered,
they belong to different