V G wrote:
> c h wrote:
>> - Start with single PC,
>> - then separate out the login/register database PC;
>> - then start adding as many PCs to do web access / file storage job as n=
eeded;
>> - the web access / =A0file storage PC would either serve the request if
>> the file is available locally,
>> - or, if the file is not available locally, the PC would ask local
>> database about which servers keep the file, and then redirect to one
>> of them.
>> - the synchronization of the local databases shoud be performed over
>> resonable time interval;
>> - you don't need RAID in my opinion, just maintain multiple copies of
>> files and place PCs at different locations; HDDs are cheap now, 2TB
>> per server seems to be a reasonable option. With reasonable
>> motherboard, RAM, and case, the server would be cheap.
>
> That sounds like a good task flow. I am still leaning towards ZFS
> RAIDZ2 or something like that.
>
> Next question is: if there are multiple servers set up to serve files,
> how will load sharing occur? How do I set up the load sharing?
>

In the beginning you could apply some simple logic, like this:
- each server would maintain the table of current load distribution
between servers, and on the request it would decide wether to serve
the request or to redirect the request to a less loaded server. The
table of load distribution should be refreshed at the reasonable rate.
Most requested files should be rellocated to less loaded servers.
Really, with your linux background you probably could cook up the
logic better than everyone on this list :-)
--

--=20
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist
.