zhangyuewen12 opened a new issue, #18292:
URL: https://github.com/apache/dolphinscheduler/issues/18292

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When using the JDBC registry , stale EPHEMERAL registry data may be removed 
from the database without correctly notifying running services.
   
   This can cause running Master instances to keep stale in-memory registry 
state.
   
   
   
   ### What you expected to happen
   
   <img width="1423" height="940" alt="Image" 
src="https://github.com/user-attachments/assets/ee4c4441-004c-4d0e-ac82-5dfe67b6f8a8";
 />
   
   <img width="1408" height="886" alt="Image" 
src="https://github.com/user-attachments/assets/52a74d2a-cd9d-434f-a28c-bdb6c4d4d427";
 />
   
   <img width="1509" height="819" alt="Image" 
src="https://github.com/user-attachments/assets/f1f913ea-ff60-4e0d-8010-2cce2f0b72ec";
 />
   
   ### How to reproduce
   
   Use JDBC registry.
   
   1.Start a Master or Alert Server instance with address A.
   2.Start a replacement instance with address B before address A is considered 
expired.
   3.Stop or kill the old instance A.
   4.Wait for JDBC registry cleanup.
   For Master:
   
   Check DB and confirm only one Master registry data row exists:
   select *
   from t_ds_jdbc_registry_data
   where data_key like '%/nodes/master/%';
   Debug or log MasterSlotManager and observe:
   currentSlotIndex = 0
   totalSlot = 2
   Check t_ds_command and observe commands that never get fetched because they 
belong to the missing slot.
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   3.4.1
   
   ### Are you willing to submit PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


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