I've setup similar solutions in the past. Nowadays I don't agree with having an ... | Hacker News

Hacker Newsnew | past | comments | ask | show | jobs | submit

		datums on Sept 28, 2009 \| parent \| context \| favorite \| on: GitHub's Architecture, before and after migration I've setup similar solutions in the past. Nowadays I don't agree with having an entire stack basically sitting idle. I prefer to get those resource involved intelligently. Looking forward to more details and possible reasons for choosing the technology (DRDB, LB software, etc )

mojombo on Sept 28, 2009 [–]

We run 12GB of memcache on each slave file server. Hardly idle!

datums on Sept 28, 2009 | [–]

I was looking at http://www.anchor.com.au/blog/wp-content/uploads/2009/09/Git... which shows file server B as a failover, traffic coming into the active LB. Does the active LB then have a pool which includes other file server B services ?

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact