>
> 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
Hi,
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 VMs it hosted are dead. Most of the time