Thanks Tom,
Balancing is solved well in this case, as we run on enterprise hardware
load balancers. They do a lot of work.
For the node grouping I think there are too few nodes to give up the half
of them for most of the time. Sadly the highest change rates occur during
the highest usage times.
B
On Thu, Oct 31, 2013 at 11:30 PM, trifo wrote:
> Thanks for the replies.
>
> Well, I forget to mention that we run on AIX, not on Linux. And so it is.
> The files MUST be consistent in any moment of time. There is a period of
> time when a lot of pages are changing in every 5 minutes.
The point r
Thanks for the replies.
Well, I forget to mention that we run on AIX, not on Linux. And so it is.
The files MUST be consistent in any moment of time. There is a period of
time when a lot of pages are changing in every 5 minutes. Well, rsync is
used to push the changes, mixed with some other tools
On Thu, Oct 31, 2013 at 09:54:14AM +0100, trifo wrote:
> I am running a web site using Apache httpd on several server nodes to
> provide high availability and performance. At present, the web content
> resides on a clustered filesystem (GPFS) to ensure that all the nodes serve
> the same content in
On Thu, Oct 31, 2013 at 4:54 AM, trifo wrote:
> I am running a web site using Apache httpd on several server nodes to
> provide high availability and performance. At present, the web content
> resides on a clustered filesystem (GPFS) to ensure that all the nodes serve
> the same content in any mo
Hi Folks,
I am running a web site using Apache httpd on several server nodes to
provide high availability and performance. At present, the web content
resides on a clustered filesystem (GPFS) to ensure that all the nodes serve
the same content in any moment.
Well, GPFS is quite an expensive produ