I would still recommend sharding. Imagine that you got 2 TB disks for a VM and
one of the oVirt hosts needs maintenance.When gluster has to heal that 2TB
file, your VM won't be able to access the file for a very long time and will
fail. Sharding is important for having no-downtime maintenance.
I can guide you through the manual approach, but I'm pretty sure that there is
an ansible role for that purpose.
Best Regards,Strahil Nikolov
On Sat, May 8, 2021 at 14:56, Ernest Clyde Chua
wrote: Good day,currently we have a 1 node host that also runs a gluster in 1
node distributed
Hello Strahil, can you point me in the right direction?, Im worried that
our data might lost in the process
On Sun, 9 May 2021, 6:08 am Strahil Nikolov wrote:
> I can guide you through the manual approach, but I'm pretty sure that
> there is an ansible role for that purpose.
>
> Best Regards,
>
Sent from my iPad
> On May 7, 2021, at 3:06 PM, eev...@digitaldatatechs.com wrote:
>
> This helps RHEL and CentOS machines utilize glusterfs and actually speeds teh
> vm up.
> I hope this will help someone. If you want the URL for the article, just ask.
I (and others) would appreciate the
Hello List,
I am facing the following issue when I try to import a VM from a KVM host to my
oVirt (4.4.5.11-1.el8).
The importing I done throuth GUI using the option of KVM provider.
-- Log1:
# cat
/var/log/vdsm/import-57f84423-56cb-4187-86e2-f4208348e1f5-20210507T124121.log
[0.0]
Good day,
currently we have a 1 node host that also runs a gluster in 1 node
distributed mode and we recently decided to upgrade to a 3 node host
which also runs gluster and set a replica count of 3.
can someone help me how can i safely change the volume type to replicated
Description of problem:
Intermittent VM pause and Qcow image corruption after add new bricks.
I'm suffered an issue on image corruption on oVirt 4.3 caused by default
gluster ovirt profile, and intermittent VM pause. the problem is similar to
#2246 #2254 in glusterfs issue and VM pause issue
7 matches
Mail list logo
