Re: High-availability with KVM?

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

 



Yes, only the VMs that reside on the node start having issues.

Also, should there be anything I have to do after bringing the node
back up and letting the heal process run?

Thanks.

On Fri, Jan 20, 2017 at 2:26 PM, Gambit15 <dougti+gluster@xxxxxxxxx> wrote:
> As long as there are enough nodes to satisfy quorum, the volumes should
> remain R/W. Have you tried writing to the volume during this period?
> Anything in your logs?
>
> Doug
>
> On 20 January 2017 at 17:06, Ziemowit Pierzycki <ziemowit@xxxxxxxxxxxxx>
> wrote:
>>
>> Hi,
>>
>> I have a 4-node gluster with distributed-replicated volumes that serve
>> out VM images.  The purpose of using gluster was to provide highly
>> available storage for our virtualization platform.  When performing
>> maintenance on one of the gluster nodes, I noticed the VM storage
>> becomes unavailable for the duration of the node being shutdown and
>> while the heal is running.  Each VM qemu process connects to gluster
>> directly and needs to be restarted in order to bring up the VM again.
>>
>> So, is the setup wrong or does gluster not provide high availability?
>>
>> Thanks,
>>
>> Ziemowit
>> _______________________________________________
>> Gluster-users mailing list
>> Gluster-users@xxxxxxxxxxx
>> http://lists.gluster.org/mailman/listinfo/gluster-users
>
>
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
http://lists.gluster.org/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