Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

What are the main drawbacks if we choose to use Node-Affinity (sticky MAC) with a load-balanced IIS solution?

We are thinking about using in-memory Session State, so need to evaluate the options.

Cheers Duncan

share|improve this question

You may get uneven balancing due to proxies, heavy users sharing the same IP, etc.

And obviously if a machine fails you lose all your sessions when users are shifted to the other machine. A disadvantage that you don't have with a hybrid system with cached state loaded from a shared backend.

share|improve this answer
Don't forget single sessions distributed across many source IP addresses. Anyone surfing with a 3G phone, for example, or anyone behind a firewall with multiple outgoing IP addresses. – bzlm Dec 17 '09 at 10:20

Primarily session state information that can get screwed up when balancing between two systems would be the primary thing to look out for. You may want to check on the serverfault meta board to ask about how this website handles sessions and load balancing (and notes for the podcast wiki), as Jeff and Joel have been very transparent about creating, configuring and modifying the ServerFault website and the issues they've run into. I'm pretty sure that Jeff discussed session issues and balance issues before.

Maybe the wiki has some info that can help. Podcast notes (telling what was in each episode) can be found on the serverfault blog.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.