Re:GitHub's Architecture, before and after migration
by datums on Monday September 28, 2009 @01:24AM
(#847866)
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 )
[ Parent
| on HN ]
Re:GitHub's Architecture, before and after migration
by mojombo on Monday September 28, 2009 @01:37AM
(#847886)
We run 12GB of memcache on each slave file server. Hardly idle!
Re:GitHub's Architecture, before and after migration
by datums on Monday September 28, 2009 @08:12AM
(#848256)
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 ?