Remove Web Application Proxy Server From Cluster -

That 0.5% of failed payments? It wasn't random packet loss. It was the cluster waiting for a dead zombie to vote.

The remaining two WAPs ( wap-01 and wap-02 ) recalculated their session tables. CPU usage on wap-01 jumped from 18% to 32%. Well within limits. Memory stable. Error rate on the payment API… held steady at 0.01% (baseline noise).

I waited ten minutes. Then twenty.

As I prepared to shut down the virtual machine, I decided to tail the legacy logs one last time. tail -f /var/log/wap/traffic.log on wap-03 .

At 2:17 AM, I drained the traffic. The F5 showed wap-03 's connection count dropping from 1,200 to 0. Beautiful. remove web application proxy server from cluster

I ran the stop command: Stop-WebApplicationProxy -Node wap-03

She paused. "The WAP server?"

But here's the terrifying part. Because wap-03 was "alive" according to basic ICMP pings, the cluster's consensus protocol had been treating it as a voting member. For six months, every time wap-03 choked on a null byte, it would delay the cluster's session replication by 400ms.