Aias00 opened a new issue, #7693:
URL: https://github.com/apache/shenyu/issues/7693

   ## Current behavior
   
   Admin considers an instance offline after 20 seconds without a report. HTTP 
synchronization reports instance presence at the start of 
`HttpLongPollingDataChangedListener.doLongPolling`, then may hold the request 
for 60 seconds (`HttpConstants.SERVER_MAX_HOLD_TIMEOUT`). The independent 
`HeartbeatListenerConfiguration` is disabled when HTTP sync is configured. With 
no configuration changes, a healthy long-polling gateway can therefore exceed 
the instance timeout before the next report. Full deployment reproduction is 
still required.
   
   Additional evidence: 
`shenyu-admin/.../listener/http/HttpLongPollingDataChangedListener.java:141-171`,
 `shenyu-common/.../constant/HttpConstants.java:37`, and the heartbeat starter 
condition.
   
   ## Acceptance criteria
   - [ ] Deterministically reproduce a healthy unchanged poll crossing the 
20-second timeout.
   - [ ] Align reporting cadence and liveness timeout, or track active polls 
with an explicit bounded expiry; a stuck request must not imply unlimited 
health.
   - [ ] Test unchanged/config-changed polls, disconnected clients, stalled 
peers and recovery.
   - [ ] Document failure-detection delay and preserve 
WebSocket/independent-heartbeat behavior.
   - [ ] Do not solve this by disabling offline detection or adding duplicate 
reporting loops without ownership.
   
   ## Source evidence
   
   [Reviewed 
source](https://github.com/apache/shenyu/blob/b4e115367fd57adc8aba332d655b1009932ba394/shenyu-admin/src/main/java/org/apache/shenyu/admin/service/impl/InstanceCheckService.java#L73).
 Baseline: `b4e115367fd57adc8aba332d655b1009932ba394`. Report based on source 
inspection; no runtime reproduction was executed during issue preparation.
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to