SkyeYoung commented on issue #12067:
URL: https://github.com/apache/apisix/issues/12067#issuecomment-3162230653

   Hi, I tried to reproduce locally based on the existing conditions you gave, 
but the result was that it did not reproduce. (APISIX: 3.13.0, 3.11.0)
   
   Please try to provide the minimal reproduction steps and environment so that 
I can assist you in locating the problem.
   
   The following are some of the results I replicated locally:
   
   <details>
   <summary>Details</summary>
   
   ```text
   Monitoring health check requests for 10 seconds...
   This will help analyze the health check frequency issue
   
   === Verifying Services ===
   Checking Docker containers:
     ✅ apisix is running
     ✅ upstream1 is running
     ✅ upstream2 is running
   
   Testing health check endpoints:
     ✅ upstream1 health check endpoint responding
     ✅ upstream2 health check endpoint responding
   
   Reloading nginx configurations...
   
   Triggering health checks by sending initial requests...
     Sending request 1 to trigger health check initialization...
     Sending request 2 to trigger health check initialization...
     Sending request 3 to trigger health check initialization...
     Sending request 4 to trigger health check initialization...
     Sending request 5 to trigger health check initialization...
   
   Waiting for health checks to initialize...
   Starting health check monitoring...
   Monitoring upstream1 health checks...
   Monitoring upstream2 health checks...
   
   === Route and Service Information ===
   [2025-08-07 02:16:27] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:27 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:27] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:27 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   Total routes configured: 600
   
   Monitoring in progress... (10s)
   [2025-08-07 02:16:28] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:28 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:28] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:28 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:29] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:29 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:29] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:29 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:30] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:30 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:30] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:30 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:31] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:31 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:31] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:31 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:32] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:32 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:32] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:32 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:33] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:33 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:33] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:33 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:34] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:34 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:34] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:34 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:35] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:35 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:35] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:35 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:36] upstream1: 172.23.0.5 - - [07/Aug/2025:02:16:36 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   [2025-08-07 02:16:36] upstream2: 172.23.0.5 - - [07/Aug/2025:02:16:36 +0000] 
"GET /apisix/heartbeat HTTP/1.1" 200 81 "-" "-" "/apisix/heartbeat"
   
   === Health Check Analysis ===
   
   upstream1:
     Total health check requests: 11
     Requests per second: 1
     Expected (1s interval): 1 request/second
     Actual vs Expected ratio: 1:1
     ✅ Health check frequency appears normal
   
   upstream2:
     Total health check requests: 11
     Requests per second: 1
     Expected (1s interval): 1 request/second
     Actual vs Expected ratio: 1:1
     ✅ Health check frequency appears normal
   
   === APISIX Control API Health Check Status ===
   Fetching health check status from Control API...
   [
     {
       "type": "http",
       "name": "/apisix/services/1",
       "nodes": [
         {
           "status": "healthy",
           "counter": {
             "timeout_failure": 0,
             "http_failure": 0,
             "tcp_failure": 0,
             "success": 0
           },
           "port": 80,
           "ip": "172.23.0.2",
           "hostname": "172.23.0.2"
         },
         {
           "status": "healthy",
           "counter": {
             "timeout_failure": 0,
             "http_failure": 0,
             "tcp_failure": 0,
             "success": 0
           },
           "port": 80,
           "ip": "172.23.0.3",
           "hostname": "172.23.0.3"
         }
       ]
     }
   ]
   ```
   
   </details>


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: notifications-unsubscr...@apisix.apache.org

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org

Reply via email to