It's really interesting that there is also a "profile" for databases available:
[root@glustera groups]# cat /var/lib/glusterd/groups/db-workload
performance.open-behind=on
performance.write-behind=off
performance.stat-prefetch=off
performance.quick-read=off
performance.strict-o-direct=on
Il 2020-10-13 21:16 Strahil Nikolov ha scritto:
At least it is a good start point.
This can also be an interesting read:
https://docs.openshift.com/container-platform/3.11/scaling_performance/optimizing_on_glusterfs_storage.html
--
Danti Gionatan
Supporto Tecnico
Assyoma S.r.l. -
Thanks for sharing.
Best Regards,
Strahil Nikolov
В вторник, 13 октомври 2020 г., 18:17:23 Гринуич+3, Benjamin Knoth
написа:
Dear all,
I add the community repository, to update Gluster to 8.1.
This fix my memory leak. But in my logfile I got every second many errors
I think that replace-brick is not the recommended way to do it... yet it's not
a bad one.
I would do the following.
1. gluster volume remove-brick VOL replica 2 Arbiter:/path/to/brick force
If you want to reuse the block device , just:
2. umount /path/to/brick && mkfs.xfs -f -i size=512
On Mon, Oct 12, 2020, 21:50 Olaf Buitelaar wrote:
> Hi Alex,
>
> I've been running databases both directly and indirectly through qemu
> images vms (managed by oVirt), and since the recent gluster versions (6+,
> haven't tested 7-8) I'm generally happy with the stability. I'm running
> mostly
Further to this - After rebuilding the slave volume with the xattr=sa
option and starting the destroying and restarting the geo-replication
sync I am still getting "extended attribute not supported by the backend
storage" errors:
[root@storage01 storage_10.0.231.81_pcic-backup]# tail
Dear all,
I add the community repository, to update Gluster to 8.1.
This fix my memory leak. But in my logfile I got every second many errors
Oct 11 11:50:29 vm01 gluster[908]: [2020-10-11 09:50:29.642031] C
[mem-pool.c:873:mem_put]
Hi Andreas,
Only step 5 should be enough. Remounting would only be required, when all
the bricks change their destination.
Best Olaf
Op di 13 okt. 2020 om 11:20 schreef Andreas Kirbach :
> Hi,
>
> I'd like to change the mount point of an arbiter brick in a 1 x (2 + 1)
> = 3 replicated volume,
Hi,
I'd like to change the mount point of an arbiter brick in a 1 x (2 + 1)
= 3 replicated volume, but I can't seem to find any information on how
to do this.
My idea is
1) Stop the arbiter brick
2) Unmount the brick
3) Change the mount point for the brick
4) Mount the brick
5) gluster
