Many thanks Strahil 😀
> On 3 Nov 2020, at 16:52, Strahil Nikolov <hunter86...@yahoo.com> wrote: > > Usually it is best practice to have the cluster expanded by a multiple of > '3' because the gluster volume is of type 'replica 3' or 'replica 3 arbiter > 1'. Such volumes can only be expanded by 3 bricks and the best practice is to > have one node per brick. > > Yet, the linux world gives freedom , so you can use 5 nodes like this: > nodeA - data, volume1 > nodeB - data ,volume1 > nodeC - arbiter, volume1 ; arbiter , volume2 > nodeD - data, volume2 > nodeE - data, volume2 > > Best Regards, > Strahil Nikolov > > > > > > > В неделя, 1 ноември 2020 г., 23:12:21 Гринуич+2, Simon Scott > <si...@justconnect.ie> написа: > > > > > > Apologies Strahill, > > I don’t think my question was very clear - my fault. > > In all the documentation on HCI that I’ve read, it clearly states the the 3 > node HCI model can only be expanded in multiples of 3 nodes, i.e. 3, 6, 9, 12. > > I don’t know if I missed a basic explanation somewhere but is there any > reason I can’t have a 5 node cluster with multiple Gluster Replica 3 volumes > utilising any of the 5 nodes in the same Gluster Peer Group? > > Kind Regards > > Shimme > >> On 1 Nov 2020, at 17:17, Strahil Nikolov <hunter86...@yahoo.com> wrote: >> >> We do not know. >> Nodes 3,4,5 need to be in the same gluster network like 1,2,3 . >> Once you create your bricks (inode size >= 512) and mount them permanently, >> you can create an extra volume or expand the current volumes. >> >> Once you have prepared the nodes, you can add them from UI. >> >> Best Regards, >> Strahil Nikolov >> >> >> >> >> >> >> В неделя, 1 ноември 2020 г., 12:44:40 Гринуич+2, si...@justconnect.ie >> <si...@justconnect.ie> написа: >> >> >> >> >> >> I have a 3 node HCI setup with 2 Replica 3 volumes using nodes 1, 2 & 3 and >> have added 2 additional Compute nodes to this Cluster. >> >> What is stopping me from adding nodes 4 & 5 as Gluster Peers and creating a >> glusterfs Replica 3 Volume using nodes 3, 4 & 5? >> >> >> Shimme >> _______________________________________________ >> Users mailing list -- users@ovirt.org >> To unsubscribe send an email to users-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/users@ovirt.org/message/4QTQLBV4MYDQ3AHWG6LD53V4T5EUDSAT/ _______________________________________________ Users mailing list -- users@ovirt.org To unsubscribe send an email to users-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/users@ovirt.org/message/73OT5JKMO2ELTBL55HA6DGRMF5PK2V3Z/
