Forum Discussion
"Drain stopping" an Exchange 2010 CAS array w/o user getting prompts.
It is my understanding the the CAS Array isn't going to cause issues, as one of the benefits of the CAS array is to allow a CAS to die and the RPC endpoint will move to another CAS without disrupting services.
Setting your node to disabled should allow (over time) connections to "drain". Unfortunately, if you've got long timeouts on your peristance profile it's possible that extremely active/chatty clients may stay connected "forever". The whole point of persistence profiles it to keep connections from drifting between nodes, so it's kind of a catch 22. Our policy is to not perform CAS maintenances during the day, but we're a 24/7 shop so that's a little more realistic for us.
John
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
