RockteMQ-AI commented on issue #1424: URL: https://github.com/apache/rocketmq-clients/issues/1424#issuecomment-6307750183
**Issue Evaluation** Category: `type/bug` | Status: **Confirmed** This is a valid bug in the Rust client's PushConsumer implementation. The root cause analysis is accurate: **Root Cause:** `PushConsumer::apply_settings` updates `PushConsumerOption` with the server-pushed `long_polling_timeout` value but does not update `SharedLongPollingTimeout`. This causes the client-side gRPC deadline to remain at the configured value (default 40s) while the request carries the server value, leading to timeout mismatches. **Impact:** Receive requests can hang up to 40s instead of the expected 20s + timeout, causing: - Longer-than-expected request latencies - Shutdown delays (as noted in #1422) - Inconsistent behavior compared to Java client **Severity:** Medium — affects performance and shutdown time, but doesn't cause data loss or correctness issues. **Dependency Note:** This bug is in code introduced by PR #1404 (currently open). The fix should either: 1. Be incorporated into PR #1404 before merge, or 2. Be addressed as a follow-up PR after #1404 merges The proposed fix (updating `SharedLongPollingTimeout` in `PushConsumer::apply_settings` like `SimpleConsumer` does) is correct and aligns with Java client behavior. --- *Automated evaluation by github-manager-bot* -- 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]
