search for: kshlmster

After nearly 3 months, we have another preview release for GlusterD-2.0. The highlights for this release are, - GD2 now uses an auto scaling etcd cluster, which automatically selects and maintains the required number of etcd servers in the cluster. - Preliminary support for volume expansion has been added. (Note that rebalancing is not available yet) - An end to end functional testing framework

Il 5 lug 2017 11:31 AM, "Kaushal M" <kshlmster at gmail.com> ha scritto: - Preliminary support for volume expansion has been added. (Note that rebalancing is not available yet) What do you mean with this? Any differences in volume expansion from the current architecture? -------------- next part -------------- An HTML attachment was scrub...

Sorry, I meant RedHat's Gluster Storage Server 3.2 which is latest and greatest. On Wed, Aug 2, 2017 at 9:28 AM, Kaushal M <kshlmster at gmail.com> wrote: > On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <markconnor64 at gmail.com> > wrote: > > Can the glusterd daemon be restarted on all storage nodes without causing > > any disruption to data being served or the cluster in general? I am > running >...

does RIO improves folder listing and rebalance, when compared to 3.x? if yes, do you have any performance data comparing RIO and DHT? On Thu, Nov 2, 2017 at 4:12 PM, Kaushal M <kshlmster at gmail.com> wrote: > On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P <amudhan83 at gmail.com> wrote: > > if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access > > volume without any challenge? > > > > I am asking this because 4.0 comes with DHT2? &...

...will continue to ship both DHT and RIO. All 3.x volumes that exist will continue to use DHT, and continue to work as they always have. You will only be able to create new RIO volumes, and will not be able to migrate DHT to RIO. > > > > > On Thu, Nov 2, 2017 at 2:26 PM, Kaushal M <kshlmster at gmail.com> wrote: >> >> We're fast approaching the time for Gluster-4.0. And we would like to >> set out the expected upgrade strategy and try to polish it to be as >> user friendly as possible. >> >> We're getting this out here now, because there w...

...(new clients unable to connect at this point) start GD2 ( necessary or does the upgrade script do this?) I assume that once the cluster had been migrated to GD2 the glusterd startup script will be smart enough to start the correct version? -Thanks On 3 November 2017 at 04:06, Kaushal M <kshlmster at gmail.com> wrote: > On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic <budic at onholyground.com> > wrote: > > Will the various client packages (centos in my case) be able to > > automatically handle the upgrade vs new install decision, or will we be > > required to...

...be the process, mostly. The upgrade script needs to GD2 running on all nodes before it can begin migration. But they don't need to have a cluster formed, the script should take care of forming the cluster. > -Thanks > > > > > > On 3 November 2017 at 04:06, Kaushal M <kshlmster at gmail.com> wrote: >> >> On Thu, Nov 2, 2017 at 7:53 PM, Darrell Budic <budic at onholyground.com> >> wrote: >> > Will the various client packages (centos in my case) be able to >> > automatically handle the upgrade vs new install decision, or will we...

if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access volume without any challenge? I am asking this because 4.0 comes with DHT2? On Thu, Nov 2, 2017 at 2:26 PM, Kaushal M <kshlmster at gmail.com> wrote: > We're fast approaching the time for Gluster-4.0. And we would like to > set out the expected upgrade strategy and try to polish it to be as > user friendly as possible. > > We're getting this out here now, because there was quite a bit of > conce...

..., Kotresh HR On Thu, Nov 2, 2017 at 4:36 PM, Amudhan P <amudhan83 at gmail.com> wrote: > does RIO improves folder listing and rebalance, when compared to 3.x? > > if yes, do you have any performance data comparing RIO and DHT? > > On Thu, Nov 2, 2017 at 4:12 PM, Kaushal M <kshlmster at gmail.com> wrote: > >> On Thu, Nov 2, 2017 at 4:00 PM, Amudhan P <amudhan83 at gmail.com> wrote: >> > if doing an upgrade from 3.10.1 to 4.0 or 4.1, will I be able to access >> > volume without any challenge? >> > >> > I am asking this becaus...

...has playbooks to automate it. At the end of this you will be left with a 4.0 cluster, but still be running GD1. Upgrading from GD1 to GD2, in 4.0 will be a manual process. A script that automates this is planned only for 4.1. > > > ________________________________ > From: Kaushal M <kshlmster at gmail.com> > Subject: [Gluster-users] Request for Comments: Upgrades from 3.x to 4.0+ > Date: November 2, 2017 at 3:56:05 AM CDT > To: gluster-users at gluster.org; Gluster Devel > > We're fast approaching the time for Gluster-4.0. And we would like to > set out the expe...

We're fast approaching the time for Gluster-4.0. And we would like to set out the expected upgrade strategy and try to polish it to be as user friendly as possible. We're getting this out here now, because there was quite a bit of concern and confusion regarding the upgrades between 3.x and 4.0+. --- ## Background Gluster-4.0 will bring a newer management daemon, GlusterD-2.0 (GD2),

On Wed, Aug 2, 2017 at 5:07 PM, Mark Connor <markconnor64 at gmail.com> wrote: > Can the glusterd daemon be restarted on all storage nodes without causing > any disruption to data being served or the cluster in general? I am running > gluster 3.2 using distributed replica 2 volumes with fuse clients. Yes, in general. Any clients already connected will still continue to work. What

Hi All, This a reminder about today's meeting. The meeting will start later today at 1500UTC. Please add topics and updates to the meeting pad at https://bit.ly/gluster-community-meetings Thanks.

This is a (late) reminder about today's meeting. The meeting begins in ~20 minutes from now. The meeting notepad is at https://bit.ly/gluster-community-meetings and currently has no topics for discussion. If you have anything to be discussed please add it to the pad. ~kaushal

Just a reminder. The community meeting is scheduled to happen in about 2.5 hours. Please add topics you want to discuss and any updates you have to the meeting notepad at [1]. ~kaushal [1]: https://bit.ly/gluster-community-meetings

Did you run autogen.sh after installing libxml2-devel? On Mon, Jan 22, 2018 at 11:10 AM, Raghavendra G <raghavendra.hg at gmail.com> wrote: > All, > > # ./configure > <success lines removed> > configure: error: libxml2 devel libraries not found > > # ls /usr/lib64/libxml2.so > /usr/lib64/libxml2.so > > # ls /usr/include/libxml2/ > libxml > > #

Can the glusterd daemon be restarted on all storage nodes without causing any disruption to data being served or the cluster in general? I am running gluster 3.2 using distributed replica 2 volumes with fuse clients. Regards, Mark -------------- next part -------------- An HTML attachment was scrubbed... URL:

...it sounds like it stops GD1. Early days, obviously, but if you could clarify if that?s what we?re used to as a rolling upgrade or how it works, that would be appreciated. Also clarification that we?ll be able to upgrade from 3.x (3.1x?) to 4.0, manually or automatically? > From: Kaushal M <kshlmster at gmail.com> > Subject: [Gluster-users] Request for Comments: Upgrades from 3.x to 4.0+ > Date: November 2, 2017 at 3:56:05 AM CDT > To: gluster-users at gluster.org; Gluster Devel > > We're fast approaching the time for Gluster-4.0. And we would like to > set out the exp...

Hey everyone, I did a quick hack in go about a month ago and gluster-rest was the outcome. You can find it at https://github.com/kshlm/gluster-rest The program is basically a wrapper around the gluster cli. It translates incoming requests to the correct gluster cli command, executes the cli command with the '--xml' parameter to get xml output and returns the xml document. For eg, For

This is combined update for the last two community meetings (because I forgot to send out the update for the earlier meeting, my bad). # Community Meeting 2017-08-02 There weren't any explicit topics of discussion, but we had updates on action items and releases. The logs and minutes are available at [1][2][3]. The minutes are also available at the end of this mail. # Community Meeting