# Scale GlusterFS Service

**URL:** <https://forums.suse.com/t/scale-glusterfs-service/1451>\
**Category:** Rancher 1.x\
**Created:** [January 13, 2016, 9:56am UTC](https://forums.suse.com/t/scale-glusterfs-service/1451 "2016-01-13T09:56:06Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![deved](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/deved/32/763_2.png) [@deved](https://forums.suse.com/u/deved)\
**Post date:** [January 13, 2016, 9:56am UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/1 "2016-01-13T09:56:06Z")

</div>

Hi,

I’m using the GlusterFS stack from the Rancher catalog. I did some experiments and it works fine, but I need some help scaling the service:

scaling the service (up and down) the gluster volume is not automatically fixed. With “gluster peer status” I see both new and old (disconnected) peers. With “gluster volume info” I see the original bricks configuration. Could you provide a guide to fix the glusterfs volume in case of service scaling? I need to replace bricks and peers. I took a look to the glusterfs documentation, but it’s not clearly explained…

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [January 13, 2016, 6:09pm UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/2 "2016-01-13T18:09:11Z")

</div>

We are just starting to add a more thorough readme for the GlusterFS service, but at this time, when scaling the GlusterFS service, the gluster volume will not be updated with the new nodes.

---

<div class="post-metadata">

**Author:** ![deved](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/deved/32/763_2.png) [@deved](https://forums.suse.com/u/deved)\
**Post date:** [January 13, 2016, 8:07pm UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/3 "2016-01-13T20:07:41Z")

</div>

Thank you Denise,  
I’ll do some experiments, if I find a solution I’ll post it there.

---

<div class="post-metadata">

**Author:** ![denise](https://avatars.discourse-cdn.com/v4/letter/d/82dd89/32.png) [@denise](https://forums.suse.com/u/denise)\
**Post date:** [January 13, 2016, 8:53pm UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/4 "2016-01-13T20:53:37Z")

</div>

The intent of the catalog is to help have people get GlusterFS setup, and at this point in time, we don’t plan on providing a managed gluster solution.

---

<div class="post-metadata">

**Author:** ![willchan](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/willchan/32/2856_2.png) [@willchan](https://forums.suse.com/u/willchan)\
**Post date:** [January 14, 2016, 1:17am UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/5 "2016-01-14T01:17:54Z")

</div>

@cloudnautique is working on improving our GlusterFS solution though. The difficult part is automatic management when new nodes are added.

---

<div class="post-metadata">

**Author:** ![withinboredom](https://sea2.discourse-cdn.com/flex022/user_avatar/forums.suse.com/withinboredom/32/808_2.png) [@withinboredom](https://forums.suse.com/u/withinboredom)\
**Post date:** [January 25, 2016, 5:05pm UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/6 "2016-01-25T17:05:42Z")

</div>

Perhaps using something like consul event handlers to manage the service?

---

<div class="post-metadata">

**Author:** ![Simone\_Fantini](https://avatars.discourse-cdn.com/v4/letter/s/b5ac83/32.png) [@Simone\_Fantini](https://forums.suse.com/u/Simone_Fantini)\
**Post date:** [May 1, 2016, 12:43pm UTC](https://forums.suse.com/t/scale-glusterfs-service/1451/7 "2016-05-01T12:43:33Z")

</div>

well, you have built the GlusterFS in official catalog, and @deved is having difiiculties with a native function of gluster: isn’t it suppose to be a distributed FS? if when scaling the main feature of gluster is not working…is not “only” our problem…

also, “at this point” we are not asking for a managed gluster solution from a open source pioneer like you, we are asking support for a native function that actualy as per @deved issue, is not working.

any, and i mean ANY help is apreciated.

thank you
