As of now, it is Dec 10th ish.
I guess, the version 7.0 is good to start using thin-arbiter if you just want to enable it for one cluster. The fixes I made are not mandatory on v7.0....
I was looking at having just one thin-arbiter for all my clusters, and hence the proposal to add volume-id etc.
Regards,
Amar
On Wed, Nov 20, 2019 at 4:05 AM David Cunningham <dcunningham@xxxxxxxxxxxxx> wrote:
Hi Amar,Thanks very much for that. I know it's probably not your responsibility, but any idea when 7.1 is likely to be in the CentOS repository?On Tue, 19 Nov 2019 at 18:13, Amar Tumballi <amarts@xxxxxxxxx> wrote:Hi David,I just updated the testing report - https://github.com/gluster/glusterfs/issues/763Looks like there are some more minor issues in v7.0. I am planning to send fixes soon, so these can be fixed in v7.1-AmarOn Tue, Nov 19, 2019 at 2:49 AM David Cunningham <dcunningham@xxxxxxxxxxxxx> wrote:Hello,I see that GlusterFS 7 is now released. The release notes don't mention Thin Arbiter, but I presume it's included? Is anyone able to comment on whether it should be considered production quality? (wondering whether to recommend to a customer or not)Does anyone have an idea when the CentOS package will be released for GlusterFS 7?Thanks in advance!On Wed, 24 Jul 2019 at 15:51, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:Hi David,This was the bug fix and it had to go to gluster 6 also in which thin-arbiter is supported with glusterd 2.However, what you were looking for was the support of thin-arbiter in glusterd which is available in gluster 7 only.So now using gluster 7.0, you can create and use thin-arbiter volume just like any other volume with few additional steps.Following is the command you can use -gluster volume create <VOLNAME> replica 2 thin-arbiter 1 <host1>:<brick1> <host2>:<brick2> <thin-arbiter-host>:<path-to-store-replica-id-file> [force]Before that you have to run thin-arbiter process on TA host.The above command you can use only with release 7 and not with older release.Patches which got merged for this change are -I am trying to come up with modified document/blog for this asap.---AshishFrom: "David Cunningham" <dcunningham@xxxxxxxxxxxxx>
To: "Hari Gowtham" <hgowtham@xxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Wednesday, July 24, 2019 5:17:50 AM
Subject: Re: Thin-arbiter questionsHello,I see references to fixes for thin-arbiter on the 6.x release notes. Does that mean thin-arbiter is ready to use on glusterfs 6 please?On Wed, 19 Jun 2019 at 17:42, Hari Gowtham <hgowtham@xxxxxxxxxx> wrote:The committing should happen a little earlier than 10th. The tagging is the one which decides if the patch makes it to the release or not and tagging happens before 10th. We do announce the tagging date for each release in the mailing list. You can keep an eye on that to know the dates. And committing in master won't be enough for it to make it to a release. If it has to be a part of release 6 then after being committed into master we have to back port it to the release 6 branch and it should get committed in that particular branch as well. Only then it will be a part of the package released for that branch.On Wed, 19 Jun, 2019, 4:24 AM David Cunningham, <dcunningham@xxxxxxxxxxxxx> wrote:Hi Hari,Thanks for that information. So if I understand correctly, if thin-arbiter is committed to the master branch by the 10th July, then it should be in the CentOS package fairly soon afterwards?I have a customer asking when we can use it, hence the questions. Thank you.On Tue, 18 Jun 2019 at 17:24, Hari Gowtham <hgowtham@xxxxxxxxxx> wrote:Hi David,Once a feature is added to the master branch, we have to back port it to the release 5, 6 and other such branches which are active. And these release branches will be tagged every month around 10th. So if an feature has been back ported to the particular release branch before tagging, then it will be a part of the tagging. And this tag is the one used for creating packaging. This is the procedure for CentOS, Fedora and Debian.Regards,Hari.On Tue, 18 Jun, 2019, 4:06 AM David Cunningham, <dcunningham@xxxxxxxxxxxxx> wrote:Hi Ashish,Thanks for that. I guess it's not your responsibility, but do you know how often it typically takes for new versions to reach the CentOS package system after being released?On Tue, 11 Jun 2019 at 17:15, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:Hi David,It should be any time soon as we are in last phase of patch reviews. You can follow this patch - https://review.gluster.org/#/c/glusterfs/+/22612/---AshishFrom: "David Cunningham" <dcunningham@xxxxxxxxxxxxx>
To: "Ashish Pandey" <aspandey@xxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Tuesday, June 11, 2019 9:55:40 AM
Subject: Re: Thin-arbiter questionsHi Ashish and Amar,Is there any news on when thin-arbiter might be in the regular GlusterFS, and the CentOS packages please?Thanks for your help.On Mon, 6 May 2019 at 20:34, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:From: "David Cunningham" <dcunningham@xxxxxxxxxxxxx>
To: "Ashish Pandey" <aspandey@xxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Monday, May 6, 2019 1:40:30 PM
Subject: Re: Thin-arbiter questionsHi Ashish,Thank you for the update. Does that mean they're now in the regular Glusterfs? Any idea how long it typically takes the Ubuntu and CentOS packages to be updated with the latest code?No, for regular glusterd, work is still in progress. It will be done soon.I don't have answer for the next question. May be Amar have information regarding this. Adding him in CC.On Mon, 6 May 2019 at 18:21, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:Hi,I can see that Amar has already committed the changes and those are visible on https://docs.gluster.org/en/latest/Administrator%20Guide/Thin-Arbiter-Volumes/---
AshishFrom: "Strahil" <hunter86_bg@xxxxxxxxx>
To: "Ashish" <aspandey@xxxxxxxxxx>, "David" <dcunningham@xxxxxxxxxxxxx>
Cc: "gluster-users" <gluster-users@xxxxxxxxxxx>
Sent: Saturday, May 4, 2019 12:10:01 AM
Subject: Re: Thin-arbiter questionsHi Ashish,
Can someone commit the doc change I have already proposed ?
At least, the doc will clarify that fact .Best Regards,
Strahil NikolovOn May 3, 2019 05:30, Ashish Pandey <aspandey@xxxxxxxxxx> wrote:Hi David,Creation of thin-arbiter volume is currently supported by GD2 only. The command "glustercli" is available when glusterd2 is running.We are also working on providing thin-arbiter support on glusted however, it is not available right now.---AshishFrom: "David Cunningham" <dcunningham@xxxxxxxxxxxxx>
To: gluster-users@xxxxxxxxxxx
Sent: Friday, May 3, 2019 7:40:03 AM
Subject: Thin-arbiter questionsHello,We are setting up a thin-arbiter and hope someone can help with some questions. We've been following the documentation from https://docs.gluster.org/en/latest/Administrator%20Guide/Thin-Arbiter-Volumes/.1. What release of 5.x supports thin-arbiter? We tried a "gluster volume create" with the --thin-arbiter option on 5.5 and got an "unrecognized option --thin-arbiter" error.2. The instruction to create a new volume with a thin-arbiter is clear. How do you add a thin-arbiter to an already existing volume though?3. The documentation suggests running glusterfsd manually to start the thin-arbiter. Is there a service that can do this instead? I found a mention of one in https://bugzilla.redhat.com/show_bug.cgi?id=1579786 but it's not really documented.Thanks in advance for your help,
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--_______________________________________________David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
_______________________________________________
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--________David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
Community Meeting Calendar:
APAC Schedule -
Every 2nd and 4th Tuesday at 11:30 AM IST
Bridge: https://bluejeans.com/118564314
NA/EMEA Schedule -
Every 1st and 3rd Tuesday at 01:00 PM EDT
Bridge: https://bluejeans.com/118564314
Gluster-users mailing list
Gluster-users@xxxxxxxxxxx
https://lists.gluster.org/mailman/listinfo/gluster-users
--David Cunningham, Voisonics Limited
http://voisonics.com/
USA: +1 213 221 1092
New Zealand: +64 (0)28 2558 3782
________ Community Meeting Calendar: APAC Schedule - Every 2nd and 4th Tuesday at 11:30 AM IST Bridge: https://bluejeans.com/118564314 NA/EMEA Schedule - Every 1st and 3rd Tuesday at 01:00 PM EDT Bridge: https://bluejeans.com/118564314 Gluster-users mailing list Gluster-users@xxxxxxxxxxx https://lists.gluster.org/mailman/listinfo/gluster-users
