This article walks through a production Redis connection timeout incident, detailing how concurrent AOF persistence and RDB snapshots caused disk I/O blockage, the diagnostic steps taken, and the optimization measures implemented to eliminate the timeouts and improve performance.
This article explains the default Tomcat settings bundled with Spring Boot 2.7.10, details core parameters such as connection queues, thread pools, keep‑alive limits, and timeouts, and demonstrates how to monitor and test these settings with code examples and network tools.
This article examines a Redis 3.x cluster failure caused by a master‑slave switch, detailing how improper Jedis timeout and retry settings triggered a service avalanche, and provides step‑by‑step analysis of the incident, code paths, and recommended configuration adjustments to prevent recurrence.
This article explains the default Tomcat configuration bundled with Spring Boot 2.7.10, details key parameters such as accept‑count, max‑connections, thread pool sizes and timeouts, shows how Tomcat’s internal threads work, provides sample YAML configurations and testing results, and offers practical tuning guidance for Java backend services.
This article investigates why DBLE repeatedly logs "no handler" messages by analyzing DBLE and MySQL logs, using Arthas to trace the call chain, reproducing the scenario with timeout settings, capturing network traffic, and explaining the MySQL 8.0.24 error‑packet behavior that leads to the observed logs.
This article explains how idle TCP connections are silently dropped by Alibaba Cloud security groups, causing Redis client timeouts and MySQL JDBC CommunicationsExceptions, and provides step‑by‑step diagnostics and configuration changes—including TCP keepalive and wait_timeout tweaks—to prevent the failures.
The article analyzes why Sysbench‑driven MySQL connections time out when concurrency exceeds 5 000, tracing the issue to TCP SYN‑cookie processing and a full accept queue, and proposes configuration‑level mitigations.
This article presents a detailed investigation of occasional Redis connection errors in a large‑scale production environment, analyzing network packets, TCP backlog behavior, Redis internal client‑cron logic, jemalloc memory reclamation, and ultimately resolving the issue by adjusting query‑buffer handling and upgrading Redis to a newer version.
The intermittent set/add failures observed with PHP’s Memcache extension 2.2.7 are caused by its built‑in 15‑second retry interval (MMC_DEFAULT_RETRY = 15) that marks the connection permanently failed after a poll timeout, and can be resolved by specifying the hidden fourth ‘timeoutms’ parameter, adjusting php.ini, or migrating to the newer Memcached extension.
When clients frequently use short TCP connections they often encounter error 110 (connection timeout) and error 99 (cannot assign requested address), which stem from TIME‑WAIT port exhaustion and server listen‑queue overflow, and this article explains the causes and practical solutions.
This article presents nine classic MySQL error cases—from connection limits and replication conflicts to installation permission issues, forgotten passwords, auto‑increment resets, character‑set garbling, binlog misconfiguration, timeout problems, and file‑open limits—each accompanied by clear diagnosis steps and practical solutions.
This article examines WeChat's Mars STN module, detailing TCP connection timeout handling, the trade‑offs between serial, concurrent and composite connection strategies, and the evolution of IP‑Port sorting algorithms—from random combinations to history‑aware and forgetting mechanisms—to achieve high performance, low load, and high availability on mobile networks.
A MySQL server experienced max_connection errors due to lingering sleep connections caused by mismatched timeout settings between LVS and HAProxy, and adjusting HAProxy's timeout resolved the issue and prevented further connection exhaustion.
This article examines three common TCP issues—missing client‑side socket timeouts leading to monitor‑killed processes, excessive TIME_WAIT sockets after service failures and their kernel tunables, and 40 ms keep‑alive latency caused by Nagle and delayed ACK—explaining kernel behavior and offering practical configuration fixes.
