Method DLedgerCommitLog.putMessages(MessageExtBatch) not implemented
See original GitHub issueMethod org.apache.rocketmq.store.dledger.DLedgerCommitLog.putMessages(MessageExtBatch)
is not implemented.
I built the new dledger-implemented rocketmq from branch store_with_dledger and wanted to try the new HA solution. But the client keeps getting “MQBrokerException: CODE: 13 DESC: the message is illegal” when I try to send a batch of messages. After debugging and making sure that there is nothing wrong with the client code, I read the server-side code and found that the batch-message putting method of DledgerCommitLog
is under development and it is returning error code of MESSAGE_ILLEGAL
.
package org.apache.rocketmq.store.dledger;
public class DLedgerCommitLog extends CommitLog {
@Override
public PutMessageResult putMessages(final MessageExtBatch messageExtBatch) {
return new PutMessageResult(PutMessageStatus.MESSAGE_ILLEGAL, null);
}
}
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (2 by maintainers)
Top Results From Across the Web
Store for RocketMQ Source Analysis - DevPress
DefaultMessageStore, which is the core entry into the storage layer. Another important thing is CommitLog. These are the three core classes.
Read more >RocketMQ笔记(十六)Broker源码分析-同步刷盘机制 - 知乎专栏
在上一篇RocketMQ笔记(十五)Broker源码分析-存储机制中我们看到最终消息存到了一个ByteBuffer中,可是有两个疑问:1.这个ByteBuffer是怎么来的呢?
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve done this. This feature relies on dledger, and the PR has been submited.
https://github.com/openmessaging/openmessaging-storage-dledger/issues/64
I meet the same problem,when will support this future @vongosling , thanks ~