4 ms·
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 int
by datums 17y ago
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 17y agoWe run 12GB of memcache on each slave file server. Hardly idle!
- datums 17y agoI was looking at http://www.anchor.com.au/blog/wp-content/uploads/2009/09/GitHubStorage_Small.png 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 ?