[Bug] [ARM] Partially acknowledged batches are not redelivered
還沒有人認領這個 Issue。
評估
- 難度
- 4/5
- 預估耗時
- 3-5 天
- 新手友好度
- 35/100
- Issue 類型
- 缺陷
- 描述清晰度
- 基本清楚
- 活躍度
- 停滯
- 技術堆疊
- cpp
研究方向
從使用 Message::getMessageId 的 Consumer::receive 迴圈和非同步 Consumer::acknowledge 路徑開始，然後在所述的 ARM 設定上重現 309 事件批次中斷。完成的標準是：僅確認批次的一部分並重新啟動後，批次中的所有事件（包括尚未接收的剩餘事件）都會重新投遞。
由索引模型根據 Issue 內容生成。
描述
Search before asking
- I searched in the issues and found nothing similar.
Version
Debian GNU/Linux 10 (buster), aarch64 (but the executable is arm32), pulsar-client-cpp 3.3.0
Minimal reproduce step
- Send a batch of events to the Pulsar broker (in our reproduction, it is a batch size of 309).
- Receive these messages (we're using
pulsar::Consumer::receivein a loop), while continuously acknowledging them asynchronously (acknowledgements are done usingpulsar::Consumer::acknowledge(const MessageId &messageId), wheremessageIdispulsar::Message::getMessageId). - Terminate the program during the middle of receiving a batch (we're terminating after having received and acknowledged the 190/309 events from a batch).
- Resume the program.
What did you expect to see?
All of the events in the batch re-sent.
What did you see instead?
None of the events in the batch, including the ones never received are re-sent.
Anything else?
- We log the result of the acknowledgement in the callback method, which shows us that the most we've acknowledged is the
190thmessage in a batch. - Exclusive subscription.
- Running it on Gravitron2/3 processors.
- We've used the same broker and test with an x86_64 Pulsar 3.3.0 Pulsar client, and we've had no issues (RHEL8).
- We can actively see missing messages - we are just sending consecutive numbers and logging them. We're missing exactly 119, the amount remaining in the batch that we've not fully acknowledged.
- We've tried not immediately terminating - i.e. we stop receiving messages but continue to process any callbacks, to validate that we're just not seeing 119 callbacks missing, and nothing.
Are you willing to submit a PR?
- I'm willing to submit a PR!
- 主要語言
- C++
- 星號
- 72
- 分支
- 93
- PR 合併指標
- 30 天內沒有已合併 PR
環境準備
- 沒有 Dockerfile 或 Docker Compose 檔案
- 有 Pull Request 範本
- 閱讀貢獻指南
從這裡開始
- 先讀完整個 Issue，再讀專案的貢獻指南。
- 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
- Fork 儲存庫，在一個分支上完成修改。
- 送出 Pull Request，並在描述裡引用這個 Issue 編號。
apache/pulsar-client-cpp 的其他 Issue
-
難度 3/5 半天 新手友好度 62/100
apache/pulsar-client-cpp#623 ·
-
[Bug] MessageTest fails to build with GCC 15.3.0 and 16.2.1 (-Werror=stringop-truncation)可能已有人在做 @davlgd 於 4 天前認領。 未關閉
難度 1/5 1 小時以內 新手友好度 25/100
apache/pulsar-client-cpp#621 ·
-
難度 4/5 3-5 天 新手友好度 55/100
apache/pulsar-client-cpp#620 ·
-
難度 4/5 3-5 天 新手友好度 48/100
apache/pulsar-client-cpp#619 ·
-
難度 4/5 3-5 天 新手友好度 20/100
apache/pulsar-client-cpp#618 ·
查看 apache/pulsar-client-cpp 的全部 Issue
相似的 Issue
-
難度 2/5 1-3 小時 新手友好度 82/100
維護者通常 1 天內回覆
-
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 3 天內回覆
-
Bug
難度 2/5 1-3 小時 新手友好度 68/100
SCIInstitute/SCIRun#2909 ·
維護者通常 2 天內回覆
-
bug libcudf
難度 2/5 1-3 小時 新手友好度 78/100
維護者通常 2 天內回覆
-
Triage: Needed
難度 2/5 1-3 小時 新手友好度 76/100
維護者通常 2 天內回覆