[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Tue, May 21, 2019 at 8:13 PM Strahil wrote: > Dear Krutika, > > Yes I did but I use 6 ports (1 gbit/s each) and this is the reason that > reads get slower. > Do you know a way to force gluster to open more connections (client to > server & server to server)? > The idea was explored sometime

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

Dear Krutika, Yes I did but I use 6 ports (1 gbit/s each) and this is the reason that reads get slower. Do you know a way to force gluster to open more connections (client to server & server to server)? Thanks for the detailed explanation. Best Regards, Strahil NikolovOn May 21, 2019 08:36,

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

So in our internal tests (with nvme ssd drives, 10g n/w), we found read performance to be better with choose-local disabled in hyperconverged setup. See https://bugzilla.redhat.com/show_bug.cgi?id=1566386 for more information. With choose-local off, the read replica is chosen randomly (based on

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

I got confused so far.What is best for oVirt ?remote-dio off or on ?My latest gluster volumes were set to 'off' while the older ones are 'on'. Best Regards,Strahil Nikolov В понеделник, 20 май 2019 г., 23:42:09 ч. Гринуич+3, Darrell Budic написа: Wow, I think Strahil and i both hit

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

Wow, I think Strahil and i both hit different edge cases on this one. I was running that on my test cluster with a ZFS backed brick, which does not support O_DIRECT (in the current version, 0.8 will, when it’s released). I tested on a XFS backed brick with gluster virt group applied and

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

Ok, so it seems that Darell's case and mine are different as I use vdo. Now I have destroyed Storage Domains, gluster volumes and vdo and recreated again (4 gluster volumes on a single vdo).This time vdo has '--emulate512=true' and no issues have been observed. Gluster volume options before

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On this one https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3.3/html-single/configuring_red_hat_virtualization_with_red_hat_gluster_storage/index#proc-To_Configure_Volumes_Using_the_Command_Line_Interface We should have the following options: performance.quick-read=off

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

OK, Can we summarize it: 1. VDO must 'emulate512=true' 2. 'network.remote-dio' should be off ? As per this: https://access.redhat.com/documentation/en-us/red_hat_gluster_storage/3/html/configuring_red_hat_openstack_with_red_hat_storage/sect-setting_up_red_hat_storage_trusted_storage_pool We

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Sun, 19 May 2019 at 12:21 AM, Nir Soffer wrote: > On Fri, May 17, 2019 at 7:54 AM Gobinda Das wrote: > >> From RHHI side default we are setting below volume options: >> >> { group: 'virt', >> storage.owner-uid: '36', >> storage.owner-gid: '36', >> network.ping-timeout: '30',

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Fri, 17 May 2019 at 2:13 AM, Strahil Nikolov wrote: > > >This may be another issue. This command works only for storage with 512 > bytes sector size. > > >Hyperconverge systems may use VDO, and it must be configured in > compatibility mode to >support > >512 bytes sector size. > > >I'm not

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Fri, May 17, 2019 at 7:54 AM Gobinda Das wrote: > From RHHI side default we are setting below volume options: > > { group: 'virt', > storage.owner-uid: '36', > storage.owner-gid: '36', > network.ping-timeout: '30', > performance.strict-o-direct: 'on', >

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

>From RHHI side default we are setting below volume options: { group: 'virt', storage.owner-uid: '36', storage.owner-gid: '36', network.ping-timeout: '30', performance.strict-o-direct: 'on', network.remote-dio: 'off' } On Fri, May 17, 2019 at 2:31 AM Strahil Nikolov

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

Ok, setting 'gluster volume set data_fast4 network.remote-dio on' allowed me to create the storage domain without any issues.I set it on all 4 new gluster volumes and the storage domains were successfully created. I have created bug for that:https://bugzilla.redhat.com/show_bug.cgi?id=1711060

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

In my case the dio is off, but I can still do direct io: [root@ovirt1 glusterfs]# cd /rhev/data-center/mnt/glusterSD/gluster1\:_data__fast/ [root@ovirt1 gluster1:_data__fast]# gluster volume info data_fast | grep dio network.remote-dio: off [root@ovirt1 gluster1:_data__fast]# dd if=/dev/zero

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

>This may be another issue. This command works only for storage with 512 bytes >sector size. >Hyperconverge systems may use VDO, and it must be configured in compatibility >mode to >support>512 bytes sector size. >I'm not sure how this is configured but Sahina should know. >Nir I do use VDO.

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

https://bugzilla.redhat.com/show_bug.cgi?id=1711054 > On May 16, 2019, at 2:17 PM, Nir Soffer wrote: > > On Thu, May 16, 2019 at 10:12 PM Darrell Budic > wrote: > On May 16, 2019, at 1:41 PM, Nir Soffer > wrote: >> >> On Thu, May

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Thu, May 16, 2019 at 10:12 PM Darrell Budic wrote: > On May 16, 2019, at 1:41 PM, Nir Soffer wrote: > > > On Thu, May 16, 2019 at 8:38 PM Darrell Budic > wrote: > >> I tried adding a new storage domain on my hyper converged test cluster >> running Ovirt 4.3.3.7 and gluster 6.1. I was able

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On May 16, 2019, at 1:41 PM, Nir Soffer wrote: > > On Thu, May 16, 2019 at 8:38 PM Darrell Budic > wrote: > I tried adding a new storage domain on my hyper converged test cluster > running Ovirt 4.3.3.7 and gluster 6.1. I was able to create the new gluster >

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Thu, May 16, 2019 at 10:02 PM Strahil wrote: > This is my previous e-mail: > > On May 16, 2019 15:23, Strahil Nikolov wrote: > > It seems that the issue is within the 'dd' command as it stays waiting for > input: > > [root@ovirt1 mnt]# /usr/bin/dd iflag=fullblock of=file >

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

This is my previous e-mail: On May 16, 2019 15:23, Strahil Nikolov wrote: It seems that the issue is within the 'dd' command as it stays waiting for input: [root@ovirt1 mnt]# /usr/bin/dd iflag=fullblock  of=file oflag=direct,seek_bytes seek=1048576 bs=256512 count=1

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

On Thu, May 16, 2019 at 8:38 PM Darrell Budic wrote: > I tried adding a new storage domain on my hyper converged test cluster > running Ovirt 4.3.3.7 and gluster 6.1. I was able to create the new gluster > volume fine, but it’s not able to add the gluster storage domain (as either > a managed

[ovirt-users] Re: [ovirt-announce] Re: [ANN] oVirt 4.3.4 First Release Candidate is now available

I tried adding a new storage domain on my hyper converged test cluster running Ovirt 4.3.3.7 and gluster 6.1. I was able to create the new gluster volume fine, but it’s not able to add the gluster storage domain (as either a managed gluster volume or directly entering values). The created