CODEWITHSUNDEEP
asp.netiissession-state
MartinHN
MartinHN

Reputation: 19802

Session State Server redundancy

We currently have an ASP.NET Web Application running on a single server. That server is about to hit the danger zone regarding CPU usage, and we want to deploy a second server.

What would be the best way to handle Session State?

We currently run InProc. But that's not an option with 2+ servers, as we want to exclude a single server from the WLB rotation sometimes to do maintenance work. Even though we use sticky load balancing, we would have to wait for all users to exit before we can exclude the server from the WLB rotation.

So I was looking at this MSDN page: http://msdn.microsoft.com/en-us/library/ms178586(VS.80).aspx

I guess my main question is: If we use the State Server mode. Can we ensure rendudancy by deploying the state server across two servers? To avoid having a single point of failure.

Upvotes: 4

Views: 2952

Answers (5)

lstanczyk
lstanczyk

Reputation: 1401

I would suggest looking into p2p Session State Server - link is here: http://www.codeproject.com/KB/aspnet/p2pstateserver.aspx

Worked for me. The only drawback is that if you have a large data set it was taking forever to replicate between peers.

Upvotes: 0

Mohamed Osman
Mohamed Osman

Reputation: 78

you might want to look into project velocity (http://msdn.microsoft.com/en-us/data/cc655792.aspx) . It has limited support now because it is on CTP3 but later this year it would be RTM. I highly suggest you watch the MIX09 session about it here

Upvotes: 0

RichardOD
RichardOD

Reputation: 29157

If you want one of the standard options I'd use SQL Server in a failover cluster. BTW have you consider memcacheddb?

Upvotes: 1

Robert Koritnik
Robert Koritnik

Reputation: 105081

Use either Scale Out State server (faster better) or SQL State (slower simpler). But beware if you store any none serializable objects into Session state, because you'll get exceptions after migration.

Upvotes: 0

TWith2Sugars
TWith2Sugars

Reputation: 3434

Sql State server would be a better option: This link might help Sql State Server . I don't believe you can run state server across multiple machines.

Upvotes: 0

Related Questions