Remove Web Application Proxy Server From Cluster Apr 2026

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).

Instantly, the average response time for the payment API dropped from 340ms to 190ms. A 44% improvement. The error rate fell to 0.001%.

"Removed a bad actor from the team," I said, sipping my cold brew. remove web application proxy server from cluster

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

Or rather, two of the WAPs did the heavy lifting. The third one, wap-03.internal.stratus.com , was the problem child. The remaining two WAPs ( wap-01 and wap-02

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

But I knew the truth. wap-03 wasn't providing redundancy; it was providing uncertainty . Its TLS cipher suite was outdated (TLS 1.0, a compliance nightmare). Its network card had a known memory leak. And worst of all, the session persistence table would occasionally corrupt, silently dropping 0.5% of payment authorization requests. Memory stable

The business didn't see 0.5%. They saw "99.95% uptime." But I saw the angry tweets. I saw the support tickets: "Card declined. Please try again." Those weren't bank declines. Those were wap-03 swallowing the requests whole.

No alerts. No 500 errors. No angry emails from the night shift fraud team.

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.