<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Thu, Dec 8, 2016 at 9:13 AM, jin deng <span dir="ltr"><<a href="mailto:cheneydeng88@gmail.com" target="_blank">cheneydeng88@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Hello world,<div><br><div> we are using glusterfs to build our public cloud storage service with NFS protocol.we use the glusterfs</div><div>as the storage layer.And we will do our development based on the glusterfs of version 3.6.9.</div><div><br></div><div> As public cloud,our users may create a lot of volumes.The way glusterfs doing is start a "glusterfsd" process</div><div>for every volume,that will make our server with too much processes and most of them may have little request.So</div><div>the processes take much resource of our server and may become the bottle of our service.</div></div></blockquote><div><br><div><br></div>Good news is we are working on brick multiplexing
which should address the issues you highlighted above and is supposed to
land in 3.10 release (Around Feb end/early March). For more details,
please refer [1]<br><br>[1] <a href="https://github.com/gluster/glusterfs-specs/blob/master/under_review/multiplexing.md">https://github.com/gluster/glusterfs-specs/blob/master/under_review/multiplexing.md</a><br><br> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><br></div><div> Two ways to solve that problem as i thought:</div><div> 1) we don't create the volume as our users indicated,instead,we create just one "basic" volume,and all the users' volumes export as a sub-directory within the basic volume.however,this solution sacrifices the ability to migrate/heal the data with the volume granularity and seems unbearable.</div><div><br></div><div> 2) modifying the protocol/server xlator to let it support handle multiple subvolumes in one process.after scanning the code of protocol/server,i think the biggest problem is the configuration,the configuration and the glusterfsd is corresponding one-by-one.I want to get some guidances from you if this modification is possible and not takes too much work.And is there other problems which this plan won't work?</div><div><br></div><div> Hope to see your solution to solve our problem.Thanks in advance.<span class="gmail-HOEnZb"><font color="#888888"><br></font></span></div></div></blockquote><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div><div><span class="gmail-HOEnZb"><font color="#888888"><div> </div></font></span></div></div><span class="gmail-HOEnZb"><font color="#888888"><br><br>-- <br><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><span style="font-family:"helvetica neue",helvetica,arial,sans-serif;font-size:15px">Sincerely</span>,<div>DengJin</div></div></div></div></div><br>
</font></span><br>______________________________<wbr>_________________<br>
Gluster-devel mailing list<br>
<a href="mailto:Gluster-devel@gluster.org">Gluster-devel@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-devel" rel="noreferrer" target="_blank">http://www.gluster.org/<wbr>mailman/listinfo/gluster-devel</a><br></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><br></div><div>~ Atin (atinm)<br></div></div></div></div>
</div></div>