similar to: gluster-rest, a RESTful web api server for gluster

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

Hi all, The meeting minutes and logs for the community meeting held on Wednesday are available at the links below. [1][2][3][4] We had a good showing this meeting. Thank you everyone who attended this meeting. Our next meeting will be on 19th July. Everyone is welcome to attend. The meeting note pad is available at [5] to add your topics for discussion. Thanks, Kaushal [1]: Minutes:

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

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

On Fri, Nov 3, 2017 at 8:50 PM, Alastair Neil <ajneil.tech at gmail.com> wrote: > Just so I am clear the upgrade process will be as follows: > > upgrade all clients to 4.0 > > rolling upgrade all servers to 4.0 (with GD1) > > kill all GD1 daemons on all servers and run upgrade script (new clients > unable to connect at this point) > > start GD2 ( necessary or

Hi Gluster users ! In the process of upgrading a Gluster 3.0.0 platform to 3.3.0, I'm trying to understand how GlusterFS 3.3.0 is working. I can't find any documentation which explains what's the role of glustershd. The only thing I (think I) understand is that the glustershd-server.vol is only generated for replicated volumes. It contains a cluster/replicate volume which replicate

Hi, dear glfs experts: I've been using glusterfs (version 3.2.6) for months,so far it works very well.Now I'm facing a problem of adding two new bricks to an existed replicated (rep=2) volume,which is consisted of only two bricks and is mounted by multiple clients.Can I just use the following commands to add new bricks without stopping the services which is using the volume as motioned?

Just so I am clear the upgrade process will be as follows: upgrade all clients to 4.0 rolling upgrade all servers to 4.0 (with GD1) kill all GD1 daemons on all servers and run upgrade script (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

Hi all I have a glusterfs cluster underpinning a KVM virtual server in a two host setup. Today the cluster just froze and stopped working. I have rebooted both nodes, brought up the storage again. I can see all the vm files there but when I try to start the vm the machine just hangs. How can I see if gluster is trying to synchronise files between the two servers? thanks Shaun -------------- next

Hello! We're restarting regular GD2 updates. This is the first one, and I expect to send these out every other week. In the last month, we've identified a few core areas that we need to focus on. With solutions in place for these, we believe we're ready to start more deeper integration with glusterfs, that would be requiring changes in the rest of the code base. As of release

Hi, I'm running GlusterFS 3.3.2 and I'm having trouble getting geo-replication to work. I think it is a problem with extended attributes. I'll using ssh with a normal user to perform the replication. On the server log in /var/log/glusterfs/geo-replication/VOLNAME/ssh?.log I'm getting an error "ReceClient: call ?:?:? (xtime) failed on peer with OSError". On the

Hi, I have a 2-node gluster with 3 TB storage. 1) I believe the "glusterfsd" is responsible for the self healing between the 2 nodes. 2) Due to some network error, the replication stopped for some reason but the application was accessing the data from node1. When I manually try to start "glusterfsd" service, its not starting. Please advice on how I can maintain

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

Hello folks, We're going to be resizing the supercolony.gluster.org on our cloud provider. This will definitely lead to a small outage for 5 mins. In the event that something goes wrong in this process, we're taking a 2-hour window for this outage. Date: Feb 21 Server: supercolony.gluster.org Time: 1000 to 1200 UTC / 1100 to 1300 CET / 1530 to 1730 IST Services affected: * gluster.org

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 scrubbed... URL:

After some test , I confirm that Esxi cann't use Striped-Replicate volume on Glusterfs's nfs. But could success on Distributed-Replicate . Anyone know how or why ? 2013/9/5 higkoohk <higkoohk at gmail.com> > Thanks Vijay ! > > It run success after 'volume set images-stripe nfs.nlm off'. > > Now I can use Esxi with Glusterfs's nfs export . > > Many

Hi Amudhan, Please go through the following that would clarify up-gradation concerns from DHT to RIO in 4.0 1. RIO would not deprecate DHT. Both DHT and RIO would co-exist. 2. DHT volumes would not be migrated to RIO. DHT volumes would still be using DHT code. 3. The new volume creation should specifically opt for RIO volume once RIO is in place. 4. RIO should be perceived as

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

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? Very short answer, yes. Your volumes will remain the same. And you will continue to access them the same way. RIO (as DHT2 is now known as) developers