apache / apache/rocketmq-client-cpp

"GetTransport of:x.x.x.x:yyyy get timed_mutex timeout" and "No route info of this topic" error while sending mq message

未關閉
#455 1 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視
主要語言
C++
星號
393
分支
167
PR 合併指標
30 天內沒有已合併 PR

描述

I used producer to send sync message , sometimes it will send failed,
error info like : ‘GetTransport of:x.x.x.x:yyyy get timed_mutex timeout' 'No route information of this topic:xxx'

[Error Detail]
[2023-Sep-09 15:59:49.902624](error):GetTransport of:172.26.89.216:10911 get timed_mutex timeout[CreateTransport:307]
[2023-Sep-09 15:59:49.902885](error):send failed of times:1,brokerName:broker-a[sendDefaultImpl:424]
[2023-Sep-09 15:59:49.902979](error):could not find property mq[selectOneMessageQueue:156]
[2023-Sep-09 15:59:49.903595](error):GetTransport of:172.26.89.216:10911 get timed_mutex timeout[CreateTransport:307]
[2023-Sep-09 15:59:49.903746](error):send failed of times:3,brokerName:broker-a[sendDefaultImpl:424]
[2023-Sep-09 15:59:49.903823](error):could not find property mq[selectOneMessageQueue:156]
[2023-Sep-09 15:59:49.904193](error):GetTransport of:172.26.89.216:10911 get timed_mutex timeout[CreateTransport:307]
[2023-Sep-09 15:59:49.904330](error):send failed of times:5,brokerName:broker-a[sendDefaultImpl:424]
[2023-Sep-09 15:59:49.904409](error):msg: No route info of this topic: audio-upload-topic,error:-1,in file line:434[send:137]

[Environment]
Centos 7
rocketmq-client-cpp-release-2.2.0.tar.gz
libevent-release-2.1.11-stable.zip

I referred to the previous issue https://github.com/apache/rocketmq-client-cpp/issues/211
It is said that this is a bug in libevent, and upgrade to version 2.1. X can solve the problem,
But why does this error still occur when we are currently using libevent-release-2.1.11-stable.zip .
Is there any other possibilities that could cause this error to occur

thankyou~

貢獻指南

開啟貢獻指南

研究方向

從 src/producer/DefaultMQProducerImpl.cpp 中第 307 行附近的 CreateTransport 和第 434 行的 send 開始。使用 libevent 2.1.11 重現逾時,然後將其行為與 Issue #211 及回報的環境進行比較。完成的標準是確認一個已確認的原因或所需設定,並記錄解決方案。

由索引模型根據 Issue 內容生成。

評估

技術堆疊
cpp
領域
networking
Issue 類型
缺陷
難度
4/5
預估耗時
3-5 天
活躍度
停滯
描述清晰度
需要釐清
新手友好度
25/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。