Gluster users - Nov 2020 - Poor performance on a server-class system vs. desktop

And you gluster bricks are localhost:/brick1 , localhost:/brick2 and
localhost:/brick3 ?
If not, add the hostname used for the bricks on the line starting with
127.0.0.1 and try again.

Best Regards,
Strahil Nikolov

? 11:18 +0300 ?? 26.11.2020 (??), Dmitry Antipov ??????:
> On 11/26/20 9:05 AM, Strahil Nikolov wrote:
> > Can you test by adding entries in /etc/hosts for the loopback ip
> > (127.0.0.1)
> > 
> > something like this:
> > 127.0.0.1   localhost localhost.localdomain
> > localhost4 localhost4.localdomain4 server
> 
> On both systems, my /etc/hosts is:
> 
> 127.0.0.1   localhost localhost.localdomain localhost4
> localhost4.localdomain4
> ::1         localhost localhost.localdomain localhost6
> localhost6.localdomain6
> 
> Dmitry
>

On 11/26/20 11:42 AM, Strahil Nikolov wrote:
> And you gluster bricks are localhost:/brick1 , localhost:/brick2 and
> localhost:/brick3 ?
> If not, add the hostname used for the bricks on the line starting with
> 127.0.0.1 and try again.
Same thing with:

127.0.0.1   trick trick.localdomain trick4 trick4.localdomain4
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6

and:

Volume Name: test0
Type: Replicate
Volume ID: 2699e6fd-3898-4912-b4de-2d3850c53fb9
Status: Started
Snapshot Count: 0
Number of Bricks: 1 x 3 = 3
Transport-type: tcp
Bricks:
Brick1: trick:/glusterfs/test0-000
Brick2: trick:/glusterfs/test0-001
Brick3: trick:/glusterfs/test0-002

When running the workload, per-interface RX/TX counters (as shown by ifconfig)
are rapidly grows on 'lo' but remains nearly the same on other
interfaces.
So I'm pretty sure that loopback is in action and the problem is somewhere
else.

Dmitry