Y98S opened a new pull request, #1050:
URL: https://github.com/apache/rocketmq-clients/pull/1050

   - Add is_heartbeat_healthy() method to Client for checking heartbeat status
   - Expose heartbeat health check in PushConsumer, Producer, and 
SimpleConsumer via public method
   - Heartbeat status is updated every 30s in client background task
   - Initialize heartbeat status as unhealthy on client creation
   - Add related unit tests to cover heartbeat health logic
   
   <!-- Please make sure the target branch is right. In most cases, the target 
branch should be `master`. -->
   
   ### Which Issue(s) This PR Fixes
   
   <!-- Please ensure that the related issue has already been created, and 
[link this pull request to that issue using 
keywords](<https://docs.github.com/en/issues/tracking-your-work-with-issues/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword>)
 to ensure automatic closure. -->
   
   [ISSUE [#1049](https://github.com/apache/rocketmq-clients/issues/1049)] 
[Rust] Add heartbeat health check API to Client
   
   ### Brief Description
   
   <!-- Write a brief description for your pull request to help the maintainer 
understand the reasons behind your changes. -->
   Add a heartbeat health check API to the RocketMQ Rust client.
   Expose is_heartbeat_healthy(), Producer, and SimpleConsumer to allow 
applications to check if the client maintains a healthy heartbeat with the 
broker. Heartbeat status is updated periodically by the client background task.
   
   ### How Did You Test This Change?
   Added and updated unit tests to verify the heartbeat health check logic in 
Client.
   Manually validated that the health status reflects heartbeat success and 
failure scenarios.
   
   <!-- In order to ensure the code quality of Apache RocketMQ, we expect every 
pull request to have undergone thorough testing. -->
   


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