Aias00 opened a new issue, #7692: URL: https://github.com/apache/shenyu/issues/7692
## Current behavior `handleBeatInfo` assigns `instanceInfo` when creating an entry, but for an existing identity it only updates `lastHeartBeatTime`. A later report with changed metadata is discarded, so periodic database synchronization and the instance page retain the initial payload. This also affects a process restarted at the same address with updated information. Reproduction: report identity A with info v1, then report the same namespace/IP/port/type with info v2; inspect the in-memory record and synchronize it to the database. ## Acceptance criteria - [ ] Existing entries accept the latest valid instance information as well as heartbeat time. - [ ] Define compatibility for missing/empty optional information; do not erase valid data unintentionally. - [ ] Test v1-to-v2 updates, persistence/query results, and namespace isolation. - [ ] Preserve the current liveness state machine unless changed separately. ## Source evidence [Reviewed source](https://github.com/apache/shenyu/blob/b4e115367fd57adc8aba332d655b1009932ba394/shenyu-admin/src/main/java/org/apache/shenyu/admin/service/impl/InstanceCheckService.java#L122). 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]
