<div dir="ltr">Hello,<div><br></div><div>I am doing that in production for web farm.</div><div>My experience:</div><div><ul><li>Gluster is synchronous (client writes to all replicated nodes), so no issue with old content</li><li>Gluster is sloooowww with small files in replicated mode due to metadata</li><li>for configuration, I ended replicating locally instead for availability</li></ul><div>So it work as you can imagine (good), just slow</div></div></div><div class="gmail_extra"><br clear="all"><div><div class="gmail_signature">Cordialement,<br>Mathieu CHATEAU<br><a href="http://www.lotp.fr" target="_blank">http://www.lotp.fr</a></div></div>
<br><div class="gmail_quote">2015-09-16 14:23 GMT+02:00 Paul Thomas <span dir="ltr"><<a href="mailto:paul@thomas3.plus.com" target="_blank">paul@thomas3.plus.com</a>></span>:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
Hi,<br>
<br>
I’m new to shared file systems and horizontal cloud scaling.<br>
<br>
I have already played with auto-scaling on aws/ec2. In term of
spawning a destroying and I can achieve that. <br>
<br>
I just want to some advice of how best implement syncing for web
files, infrastructure, data, etc.<br>
<br>
I have pretty much decided to put the database side of things on a
private instance. <br>
I'll worry about db clustering later I’m not to bothered about this
not, because the software supports it.<br>
<br>
It seems logical to put the web folder / application layer on a
shared file system, maybe some configuration too.<br>
<br>
What I'm really unsure about is how to ensure that the current
system is up to date and the configuration tweaked for the physical
specs.<br>
<br>
How do people typically approach this? I'm guessing it not always
viable to have a shared file system for everything.<br>
<br>
Is the approach a disciplined one? Where say I have development
instance for infrastructure changes. <br>
Then there is a deployment flow where production instances are
somehow refreshed without downtime. <br>
<br>
Or is there some other approach?<br>
<br>
I notice on sites like yahoo, things are often noticeably unsynced,
mostly on the data front, but also other things. <br>
This would be unacceptable in my case.<br>
<br>
I appreciate any help I can get regarding this. <br>
<br>
My typical load is from php-fpm/nginx processes, mysql bellow this.
<br>
<br>
Should the memory cache also be separated, or as I think it is quite
good for this to be divided up with the infrastructure to support
each public instance individually? <br><span class="HOEnZb"><font color="#888888">
<br>
Paul<br>
</font></span></div>
<br>_______________________________________________<br>
Gluster-users mailing list<br>
<a href="mailto:Gluster-users@gluster.org">Gluster-users@gluster.org</a><br>
<a href="http://www.gluster.org/mailman/listinfo/gluster-users" rel="noreferrer" target="_blank">http://www.gluster.org/mailman/listinfo/gluster-users</a><br></blockquote></div><br></div>