Slashcode Log In
Building a large Slash cluster
The entire cluster will be x86 boxes running FreeBSD. We're planning on keeping our own copy of Slashcode CVS up-to-date and running the same version that powers Slashdot.org, but with a fair amount of custom tweaks and plugins.
In addition to raw serving power, this cluster needs to be available. If any single machine dies we want to switch its tasks over to another machine for a short period of time while the dead box is fixed/replaced and brought back online. So here's the idea:
5 server-class machines:
Each box is a 1-processor 1.2 GHz P4 and single IDE system disk. Question: How much memory would you put in these?
- 1 firewall stateful packet filter, doubling as a load-balancer for the 2 webservers listed below, and with the ability to run as a backup SMTP machine
- 1 DNS/SMTP machine with the ability to run as a backup firewall
- 2 webserver boxes each running Apache
- 1 webserver running Apache dedicated to serving images and also serving some corporate backend stuff.
Both boxes are dual-processor 2.x GHz P4 with multiple SCSI disks. Questions: How much memory would you put in these? How would you arrange the drives?
- 1 primary dataserver machine dedicated to running mysqld, but with the ability to run a backup slashd, nfsd, and loghost
- 1 backup dataserver running a slave mysqld to the primary dataserver, slashd, nfsd (to serve slashd-generated SHTML to the 2 webservers, and acting as a syslog loghost