Dear Ravi,
Again thank you very much for your response. I did experiment a bit further in
my scenario, with the following result:
I could leave 4.1.6 for the smaller machines with all SSD. The performance does
seem to be a bit lower compared to 3.12.15, but within a bearable range. For me
the tradeoff is more time until EOL vs. performance.
For the larger pair of machines with 1 x SATA SSD and 1 x fast SAS HDD, I did
NEED to migrate back to 3.12.15 and stay at that. There, gluster volume heal
<volname> info does not always show healing, but when writing is heavy,
the system temporarily lists shards for healing. That does seem to bring the
overall performance down. My settings are features.shard on,
features.shard-block-size 512MB, cluster.data-self-heal-algorithm full and
performance.low-prio-threads 32.
Is there a way to cure the performance drop while using the more modern versions
of Gluster?
Regards,
Michael
-----Urspr?ngliche Nachricht-----
Von: Prof. Dr. Michael Schefczyk
Gesendet: Mittwoch, 12. Dezember 2018 07:55
An: gluster-users at gluster.org
Betreff: AW: Gluster 4.1.6 slow
Dear Ravi,
Thank you for your response. While performance was slow, there were no volume
heal tasks pending. All analysis using the usual commands (volume status, volume
info, volume heal $volname info) did not show issues. One could kick off volume
heal without adding "info" (e. i. gluster volume heal $volname) which
would show no issues as well.
Regards,
Michael
-----Urspr?ngliche Nachricht-----
Von: gluster-users-bounces at gluster.org <gluster-users-bounces at
gluster.org> Im Auftrag von Prof. Dr. Michael Schefczyk
Gesendet: Dienstag, 11. Dezember 2018 08:33
An: gluster-users at gluster.org
Betreff: Re: [Gluster-users] Gluster 4.1.6 slow
Dear All,
Investing a few hours, I did revert to Gluster 3.12.15 from the oVirt
repository. With the same settings, the system does work as fast as before. That
required two tries. It looks like restarting Gluster after volume deletion and
downgrade was not enough. The system needed to be rebooted.
The uncomfortable thing is that it is not obvious why the problem did happen and
if it will happen again once an upgrade from 3.12.15 becomes more pressing.
Regards,
Michael
_______________________________________________
Gluster-users mailing list
Gluster-users at gluster.org
https://lists.gluster.org/mailman/listinfo/gluster-users